Search results

Check out the NZ() function

Typically, if you can calculate a value there is no need to store it in the table. Just recalc when necessary

I believe that the sample I've posted in the SAmple Databases area might be of some help. http://www.access-programmers.co.uk/forums/showthread.php?t=103456

I get that every so often.. Check the margins and set them smaller

Have you tried to compile and see what errors you pickup? Try going into a form module since you get into a regular module

The update query certainly does fix your problem. Please find attached a solution.

With this many records you may well exceed the MaxLocksPerFile. You may want to reset this value from the default value of 20,000 ... maybe you should set it to around 200,000.

just use an Update Query

You can try using the following Sleep function Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long) Sleep 4000 ' this will sleep for 4 seconds

try FindFirst instead of FindLast

This is not an appropriate posting for this site. Maurice

Hi Sheila - the example that I have posted in this forum may be of some help to you. http://www.access-programmers.co.uk/forums/showthread.php?t=103387 Best regards Maurice

Too bad you can't download anything because I've posted a sample database that meets your requirements. http://www.access-programmers.co.uk/forums/attachment.php?attachmentid=12904&d=1141829591

Thank you for your post, however we have some 10 different posts on this subject

The rule has always been that if you can calculate it, then you don't have to store the result. Just recalculate when needed

You may want to lookup Workgroup files (.MDW)

In the After Update event, try Me.refresh

Open the database ( start it up ) ...go into any module ( view the code ), of either a module, a form, a report, etc... then from the Toolbar ( top of the screen ) select Debug and select the Compile item.

Just make sure you can compile to an .EXE before you get too far into it. As far as I know, I don't think you can with the Express Edition... I think it's only a learning edition.

The word is that Microsoft will no longer support Data Access Pages after this year. Since the project is obviously done in Access then you should run it in it's native environment.