Recent content by DennisOJensen

I concur -- but I do not feel like once again troubleshooting another issue with a Microsoft product at this time. Done that too many times already because it was absolutely necessary for at the time there was simply no work around for it.

Check got that and in case it came across wrong was not slamming your code either, just trying to put out a comment about the implicit versus explicit conversion. As a note I did state that my code was not "exact syntax" which implied the person using it needed to check for the proper syntax...

First no apology needed -- input is always welcome. I doubt its speed the unit I have is not a powerhouse in fact it is barely a development machine -- prior to getting a memory upgrade the thing only had 4MB of Ram no it has a whomping 8MB. Still I have worked with a lot of event handling...

Well I would not call that more friendly. A bit more streamlined but with an implicit conversion something I have found from time to time can cause issues. Still I've been working with visual basic since version 3 and C so I tend to play it more cautiously and make sure I am explicit about...

Yep you might not ever encounter the issues behind autonumbers but I get to work on systems that border on or need to move to a bigger database as access does have its limits and the headache of autonumbers has been one of the issues I have to deal with for more than one customer. Which can...

Okay I was just correcting what you had posted -- as what you posted would only give you the last value as you overwrite the first 2 Okay to collect all the Errors into one field you are either going to have concatenate them or you have to have a field that supports multiple rows of data --...

To clarify a point, because sometimes I get my database software confused, one of Microsoft's products has a data type called "Calculated" which means you can add this to your table and it does the "calculation" every time a new record is added or an update to a record that changes a value used...

Okay fairly simple really :) and not an uncommon mistake try this just before the Debug.Print line instead of what you currently have -- that is if I am understanding correctly what you are trying to do strErrSum = Me![ErrSum] & strCieVal & ";" & strAcctVal

Did you use the one I posted ? Back to you ? I am pretty sure I gave you the new one. Does the new one have 3 tables now? I mean I tested it and got the cmdAddUpdate button -- Update functionality working and figured I would let you test the rest.

Okay I found the issues -- you were setting some of the values incorrectly and then you were doing the Requery on the wrong Form I have cleaned up the code added a few items that you should always have (aka Errorhandlers) and set it so your Comboboxes are based on table data instead of hard...

And be warned some things like auto-updating of tables takes place which can cause bad data to get into your database which is just one of the headaches of bound controls I am stating this mainly as an answer to vbaInet's question. There are others but I do not recall them all off the top of my...

Okay I reformatted your code and added few items to help with checking for errors -- which need to be part of every function/subroutine unless you are absolutely 100% positive without a shadow of a doubt sure there could not ever be an error occurring within that function/subroutine. Glancing...

Okay I differ in opinion than with gemma -- personally I try to guide newbies away from bound controls because there are so many inherent little issues that if you are not familiar with -- can cause you a world of headaches. I have not only seen this used in access but I have seen it used in...

Personally this is one of those reasons I do not use data binding - once the change has been made they click the Save button and that handles the process if the database is separate from the front-end then my front end has a set of update tables in case the connection to the back-end is broken...

Data Binding: This is the where the fields and views of the User Interface (front-end) are connected directly to the back-end database tables. Such that if you make a change to something on the front-end it is reflected in automatic changes to the back-end.