Database Front / Back end

[Sarah M]

Would someone be able to provide some instrustions on how to do the
following?

Currently our client has a 97 database. Some of the machines have 97 and
some have 2002. I was under the impression you could create two seperate
"front-end"s, one for each version, and have them access the same data.

Can this easily done without re-creating too much (there are lots of forms,
reports etc..?) If so could someone provide some instructions?

Or is there another way 97 and 2002 coudl work together?

Many Thanks in advance.

 

[John]

Are the tables linked to external tables? If so, I don't see why you
couldn't convert the 97 to 2002 for those users who don't have 97 because
each front end would still be pointing to the same data.

 

[Tony Toews]

Would someone be able to provide some instrustions on how to do the
following?

Currently our client has a 97 database. Some of the machines have 97 and
some have 2002. I was under the impression you could create two seperate
"front-end"s, one for each version, and have them access the same data.

Yes. Assuming the backend (BE) on the server stays in A97 format.

Can this easily done without re-creating too much (there are lots of forms,
reports etc..?) If so could someone provide some instructions?

Just convert the FE to A2002 which should go relatively smoothly.
There are some problems but nothing serious.
Access 2.0 and Access 97 to Access 2000/2002 conversion problems
http://www.granite.ab.ca/access/conversionproblems.htm

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

 

[Sarah M]

Just convert the FE to A2002 which should go relatively smoothly.

There are some problems but nothing serious.

Do I need to do the following?

1. Split DB
2. Make 2 copies of FE
3. Use Original for 97
4. Convert the other for 2002

Are there any drawbacks to using this approach? Can I put the DB back to ONE
mdb in the future if I wnated to?

Thanks again.

 

[Tony Toews]

Do I need to do the following?

1. Split DB
2. Make 2 copies of FE
3. Use Original for 97
4. Convert the other for 2002
Correct.

Are there any drawbacks to using this approach?

Not really. A client has been happily running A97 and A2000 FEs
against an A97 BE for a year and a half.

Can I put the DB back to ONE mdb in the future if I wnated to?

Yes by deleting the linked tables and reimporting the tables and
relationships. However you really don't want to as multiple users in
a FE MDB or combined MDB is troublesome and prone to corruptions
especially in A2000 and newer.

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

 

[Sarah M]

However you really don't want to as multiple users in

a FE MDB or combined MDB is troublesome and prone to corruptions
especially in A2000 and newer.

Are you saying that if you are having multiple users it should be set up as
a FE/BE regardless of the version / version(s) od access?

Thanks again for all your help.

 

[Sarah M]

Can multiple users share the same mdb or do I need a copy of the mdb for
every user?

Also, Am I able to keep the oriinal FE mdb in tact, copy it and make an mde
for each user?

Thanks again

 

[Tony Toews]

Are you saying that if you are having multiple users it should be set up as
a FE/BE regardless of the version / version(s) od access?

Correct. And each user gets their own copy of the FE MDB/MDE.

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

 

[Tony Toews]

Can multiple users share the same mdb or do I need a copy of the mdb for
every user?

Each user gets their own copy.

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 Auto FE
Updater utility 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.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating a directory named after the user on a server. Given
a choice put the FE on the Citrix server to reduce network traffic and
to avoid having to load objects over the network which can be somewhat
sluggish.

Also, Am I able to keep the oriinal FE mdb in tact, copy it and make an mde
for each user?

You'd best keep the MDB once you make an MDE or you'll never be able
to update the MDE. <smile> This is a one way process.

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

 

[Sarah M]

Tony,

Many thanks for all your help. Just 2 more questions.

1. Does the FE all need to be the same name? For example if it was on a
network drive can I create FE1 and copy it as FE2, FE3 ect and all be in the
same dir as the BE?

2. Do I create the mde for 97 and let the 2002 machines convert or do I
create two seperate mdes?

Thanks again, your advise has been most helpful.