Problems with 2 Different Versions of MSACCESS 2003

[Guest]

We have a database developed in MSACCESS 2000 using VBA for most of the
programming.

This database has opened and performed just find in MSACCESS 2003 until
recently when it was distributed to 250 new PCS.

The code bombs all of a sudden. We have narrowed down the problem. The
older PCs are running MSACCESS 2003 Version 11.0.6566.0 and the new PCs are
running MSACCESS 2003 Version 11.0.5614.0.

It runs just wonderful on all pcs running the older version and bombs on all
new pcs with the 5614 version.

Problem - the 250 new pcs are all field staff and have been sent out from
one end of the state to the other all ready. This is a standalone system.

Any one else ran into this problem or any solutions. We are looking at
having to recall all the machines back to Springfield IL and rewrite the
database, since we're not sure what changed between the 2 versions of 2003
Access.

Thanks!!

 

[Douglas J. Steele]

Your version numbers seem to imply that the "older" PCs are actually running
a new version of Access 2003 than the "new" PCs. Can you not get the service
packs applied to the new machines?

It's entirely possible that you've got a problem with the References
collection, caused by differences in the version between the machine on
which the application was developed, and the machines on which it's being
deployed.

 

[Guest]

We wondered if it could be that a patch was missed on the new PCs.

Any idea where on MS website to find the patches?

THANKS a bunch!

 

[Douglas J. Steele]

Do a search at http://download.microsoft.com

 

[George Nicholson]

Run them through Windows Update *and* Office Update (or the one-stop
Microsoft Update).

If the "new" machines are just now using Access 2003 for the first time,
make sure they have all the JET Service Packs so that sandbox mode either
works or doesn't break Access apps (and those are the only 2 possibilities.
Sandbox mode can't be safely ignored unless JET is up to date, and it needs
Jet to work properly). JET updates are part of the OS, not Office or Access.
Access 2003 requires at least Jet 4.08 to work properly.

http://support.microsoft.com/kb/239114/en-us
How to obtain the latest service pack for the Microsoft Jet 4.0 Database
Engine

HTH,

 

[Tony Toews [MVP]]

The code bombs all of a sudden.

What code bombs? What's the exact error message?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Todos Menos [MSFT]]

Tony

I never claimed to be an employee of Microsoft
SERIOUSLY DUDE GIVE UP


I just choose to list my 'favorite stock to short' in my caption


You _PLEASE_ tell me where I'm claiming to work for Microsoft.
I never agreed to those terms and conditions.


AND I HAVE NO PROOF THAT YOU ARE AN MVP!


a) I am right
b) you have credibility because you're an MVP
c) you should be using your MVP in order to get MIcrosoft to STFU and
fix bugs
d) you are a waste of space because you haven't grown past DAO and
MDB


until you lose the training wheels; stick a fork in it, kid


MS SELLS BUGGY SOFTWARE AND I AM DONE ACCEPTING MEDIOCRITY


they need to start testing this shit; before they sell it-- instead
of
focusing on IPTV and Xbox and Zune and inventing new .NET _CRAP_

 

[Todos Menos [MSFT]]

I'd reccomend moving away from DAO

ADO is always faster and DAO hasn't been included with Windows, Office
or MDAC for a decade

 

[Todos Menos [MSFT]]

uh.. let me guess a classic DAO hang?

you close the database but Access won't close?

Closing objects in a particular object?
YOU KIDS SHOULD HAVE MOVED TO ADO A LOONG LONG TIME AGO
ADO is faster for _EVERYTHING_

Case Closed