Acess 2000 // XP User Issue

  • Thread starter Thread starter Carina Prakke
  • Start date Start date
C

Carina Prakke

We have a database in MS Access 2000 in Windows 2000. It
has worked fine until a few users who had upgraded o/s to
Windows XP went into it.

I'm trying to decipher whether the XP users caused a
problem or not - does anyone know if XP is incompatible
with Windows2K-based databases in Access?

It seems unlikely, but I'm trying to start somewhere (!)

Thanks!
Carina
 
Carina,

They are fully compatible. What are the problems that you
are having?

Gary Miller
Sisters, OR
 
Gary,
I can open the database, go to the PO Form from the
switchboard, and when in the PO I want to "Preview PO"
(which would open PO Report) I get the error message
" MSAccess.exe Application Error
The instruction at "0x77fc8fe1" referenced memory
at "0x6a921e12". The memory could not be "written".
Click on OK to terminate the program. "
At this point, I get kicked out of Access completely.

I've tried "Detect & Repair", I've re-booted several
times, I've had other W2K machines try it and we all get
booted.
When IS tried to help, they (with their W-XP machine) had
no problem viewing the PO/report. (aagghh!)

Also, as a note, my other Access databases work fine.

Thanks!
Carina
 
Carina,

If your other databases all work fine, it is probably not a
general Access2K/XP problem. Interesting that the same db
opens on another XP machine.

You may have some type of corruption in the db itself. Try
creating a new empty database and import all of the objects
from the original into it and see what happens when you try
and run it.

It is also well possible that the PO report could have
gotten corrupted if that is the only place that you are
getting the error.

Are you on a network with a FE/BE setup? If so you may try
copying in someone elses front end and see how that one
works.

Gary Miller
Sisters, OR
 
Got me stumped, too. :)
Nope, no FE/BE - everyone just logs straight in to Access
db.
I'll try copying, though, and see what happens.
Thanks for the idea.
Carina
 
No luck on the import, Gary. Same error messages come up.
I'm going home (4pm here) and I'll battle it fresh again
on Monday.
Thanks for brain-storming with me.
Carina
 
I would be very wary of opening the same database using different versions
of Access, especially opening it *concurrently*.

The likely cause in the References Collection. AXP and A2K have different
set of References (for example, the Access Object Library version 9.0 for
A2K and version 10.0 for AXP).

It is ***possible*** that when a database previously used in A2K (hence
Access O.L. 9.0 in the References) is opened in AXP, AXP may need to change
the Reference to Access O.L. 10.0 since the PC doesn't have Access O.L. 9.0
if you upgraded Office / Access and the Access O.L. 9.0 was removed. Thus
the database is now flagged to use Access O.L. 10.0. After that, when A2K
users try to open the database, A2K software may not be able to recognise
and resolve the Reference to Access O.L. 10.0 (since Access O.L. 10.0 comes
out AFTER A2K) and therefore, your database won't work properly in A2K.

I would suggest splitting the database urgently and give each user a copy of
the Front-End on his/her desktop (before your database is corrupted beyond
repair). Since each user has his/her own copy of the Front-End, the
Front-End can have the Refernces approriate for the Access version installed
on the PC.

HTH
Van T. Dinh
MVP (Access)
 
Thanks Van.

This seems very likely since the troubles started after
one of the staff accessed it from XP. I've gone to IT and
asked them to restore the db from a backup taken before
the glitches appeared. Hopefully that will work for now.

I need to read up on splitting a database into FE/BE - I
understand why it would be safer, but I just don't have
the knowledge base yet. For the time being, I'm going to
request that XP users don't use the database.

Thanks for your help on this!
Carina
 
Carina Prakke said:
I need to read up on splitting a database into FE/BE - I
understand why it would be safer, but I just don't have
the knowledge base yet.
Click to expand...

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at my website for more info. See the Auto FE Updater downloads page
at my website to make this relatively painless.. It also supports
Terminal Server/Citrix quite nicely.

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
 
Back
Top