By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,635 Members | 913 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,635 IT Pros & Developers. It's quick & easy.

Access 2K Conversion

P: n/a
Hello all,

Quick question. I have several users using Access 97 and several
using Access 2K. The db is written in 97. I want them to exist
together peacefully but sometimes the db gets corrupt due to someone
accidentally trying to convert it i think.

anyway, i tried to split the db, so there are 2 front ends, 1 in 97
and 1 in 2k. this is fine except the performance is so slow even
after making the fronts .mde files.

If i went back to just a 97 db, is there a way to stop access2k from
automatically comming up with the screen asking them if they want to
convert?
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
http://support.microsoft.com/default...b;en-us;275164

Regards

Peter Russell

Berae previously wrote:
Hello all,

Quick question. I have several users using Access 97 and several
using Access 2K. The db is written in 97. I want them to exist
together peacefully but sometimes the db gets corrupt due to someone
accidentally trying to convert it i think.

anyway, i tried to split the db, so there are 2 front ends, 1 in 97
and 1 in 2k. this is fine except the performance is so slow even
after making the fronts .mde files.

If i went back to just a 97 db, is there a way to stop access2k from
automatically comming up with the screen asking them if they want to
convert?


Nov 12 '05 #2

P: n/a
dk******@yahoo.com (Berae) wrote:
Quick question. I have several users using Access 97 and several
using Access 2K. The db is written in 97. I want them to exist
together peacefully but sometimes the db gets corrupt due to someone
accidentally trying to convert it i think.
Probably not. A client has been happily running 10-15 users on an A97 FE and 10-15
users on an A2000 FE sharing an A97 BE for almost a year. See the Access Corruption
FAQ at my website for some tips and things to help locate the problem.
anyway, i tried to split the db, so there are 2 front ends, 1 in 97
and 1 in 2k.
Not only do you want to split it each user should get their own copy of the FE. A
shared A2000 FE corrupts much quicker than a shared A97 FE.

I specifically created the Auto FE Updater utility so that I could make changes to
the FE MDE as often as I wanted and be quite confident that the next time someone
went to run the app that it would pull in the latest version. For more info on the
errors or the utillity see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.
this is fine except the performance is so slow even
after making the fronts .mde files.
The three most common performance problems in Access 2000 are:
- LDB locking which a persistent recordset connection or an always open bound form
corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and links to MS KB
articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm
If i went back to just a 97 db, is there a way to stop access2k from
automatically comming up with the screen asking them if they want to
convert?


Yes, but don't.

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
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.