Search results for query: *

Autonumber does not give you consecutive numbering (unfortunately). Well it does, but if you cancel a new record creation you lose the number it used, hence the gaps. To maintain an unbroken sequence you will have to manage your own PrimaryKey number which entails storing the number in a...

I am from a coding background and was at a company for many years where applications (not just access) had to be user idiot proof in every respect. Literally controlling every entry in terms of validity and data relationships (A value in one field governing possible values in others etc etc) I...

Hi I created a test table with your 3 pieces of information Colour ID Type I then keyed in the values you quoted on the example The query below will give you the counts. You basically include your table of data on the Query, click the tool bar TOTAL icon (Looks like the E) That will give...

Never mind, Worked it out. Another on of Access'es Idiosyncrasies. Going into design mode/ vba debug does an exclusive lock on the DB. Had my breakpoint before the .open so it was locked before the command was called. Did my breakpoint after the open command and it worked [ponder]

I am developing an App in Access 2003 and prior to this have always used DAO for the coding. (I know, get with the times etc [pipe]) I thought I would use this project to move to ADO but have come across a problem. I was trying to do an ADO connection so I could use a transaction around a...

Ditto vbajock Only found CurrentProject.Connection in an example. No actual reference in help detailing how to connect to local DB. Searching thru help for something, sorry to boost an old post but felt compelled to confirm MS documentation shortfalls.

Found out reason, I was initialising a combo box with valid values based on another combo box, changed the initialise to recongnise me.newrecord and not change value and it now does the UNDO without calling the BeforeUpdate. Suppose it was doing what it should, just took a nights sleep to come...

Hi, I have a form associated with a recordset. I can navigate through back and forward and make changes quite happily. The problem occurs when I try to cancel partial entry of a NEW record. I have my form validation code in the form_beforeupdate event to verify all the fields are populated and...

Glad I am not the only one who thinks subforms are awfully implemented. I will only use to do some static displays. Anything that needs an ounce of control or complexity rules out a subform for me. I end up coding my own "form in a form" setup. Should not have to do it though.