Run-time error 29068 with Access 2003

[makyland]

Hi! I'm simultaneously working in developing 2 different Access 2003
applications with VBA, but changed to a new laptop this week. Unexpectedly I
get run-time error 29068: "Access cannot complete this operation. You must
stop the code and try again" whenever I try to save a form in the close
event. I had never experienced it before in any of the computers I have
installed my applications before... and now it's occuring in both
applications. The piece of code is as simple as:
Sub Form_Close()
DoCmd.Restore
DoCmd.Save acForm, Me.Name
End Sub
and it always worked before. Any idea what it can be due to? I have upgraded
my Office 2003 installation with Service Pack 2 already...
Thank you in advance for any help on that!!!!!

 

[Tim D]

Hi! I'm simultaneously working in developing 2 different Access 2003
applications with VBA, but changed to a new laptop this week. Unexpectedly I
get run-time error 29068: "Access cannot complete this operation. You must
stop the code and try again" whenever I try to save a form in the close
event. I had never experienced it before in any of the computers I have
installed my applications before... and now it's occuring in both
applications. The piece of code is as simple as:
Sub Form_Close()
DoCmd.Restore
DoCmd.Save acForm, Me.Name
End Sub
and it always worked before. Any idea what it can be due to? I have upgraded
my Office 2003 installation with Service Pack 2 already...
Thank you in advance for any help on that!!!!!

Do you mean Service Pack 3, because your error sounds like one caused by
bugs in SP3. If so, take a look at the yellow box headed 'New bugs in SP3 for
Access 2003' at http://allenbrowne.com/tips.html. I will bet that bug 1 or
bug 2 in the list is the source of your problem.
HTH.

 

[makyland]

No, I meant SP 2.
I'm observing now though that in the laptop where I'm experiencing the
problems I have:
Microsoft Office Access 2003 (11.6566.6568) SP2
while in the previous one where I don't have this problem at all the version
is:
Microsoft Office Access 2003 (11.6566.8107) SP2
so I guess that maybe the difference .6568 to .8107 is causing the problem????
I thought the update I installed yesterday was full SP2 but looking at this
it might be that I still need something else right?
I didn't want to upgrade to SP3 because I had heard of some problems with
it. Is it recommendable to upgrade?

 

[Tim D]

The decision whether to upgrade to SP3 is not simple, and depends on factors
that only you can evalute. An important factor is which version of Office
users of your apps will be using. The best I can do is suggest several links
below that are worth reviewing rather carefully.

But the first thing is to know accurately which version of Access you have
on your PCs. This point has to be made because you may NOT get the true
version by looking at Help / About Microsoft Access! To see why this is so:
http://support.microsoft.com/kb/328294/

This is a list of Office 2003 SP versions:
http://support.microsoft.com/kb/821549/

This tells you about Jet versions:
http://support.microsoft.com/kb/239114/
Note that it is important that all users connecting to a back-end data mdb
should be using the same version of Jet.

Best to use code to get the current versions of Access and Jet. I have found
Allen Brownes 'Get version' code to be excellent. It is included in his
'Splash Screen' download:
http://allenbrowne.com/ser-53.html

MS list of Known Issues in SP3 is in this article:
http://support.microsoft.com/kb/923618
Note that this list does not include the most common gotchas, again from
Allen Brownes site:
- "Combo is blank if RowSource table field has a Format property entry"
- "Access crashes if RowSource is a table with more than 31 fields"

My own experience with SP3 has been:
a) I had to tweak a number of controls in my apps
b) Once the mods were done, my apps seem fine in SP3
c) The apps still work ok under SP2.

I hope this helps.
Tim