Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access 2000 frontend with 97 backend 1

Status
Not open for further replies.

sera

Technical User
Jun 29, 2000
360
US
Has anyone tried to create an Access 2000 front end to an Access 97 backend? I have users that are using both 2000 and 97 and I need them all to be able to access the database. So I was thinking that it is possible that I create a 2000 front end and a 97 front end. But I am assuming that the backend would need to remain in Access 97. Has anyone done this, and has it caused you any problems?



Sera
I often believe that...
My computer is possessed!
 
Sera,

Yes, what you would like to do is certainly possible.

Your backend can be any prior version of access. New Microsoft Access is aware of all older versions of Access.

So, I would suggest Creating your backend in Access 97 (Since this appears to be the oldest version that your users have installed)

Second, I would develop the frontend in Access 97 and when this is complete, I would make a copy and then use your latest version of Access to upsize to Access 2000. Make sure you compile after Upsizing.

By doing this, you only need to maintain one true version for development.

Yes, this works fine. I have several projects working like this with no problem.

Hope This Helps,
Hap [2thumbsup]

Access Add-on developer [pc] - [americanflag]
 
Good this makes me very happy...thanks very much.


Sera
I often believe that...
My computer is possessed!
 
A system I set up I had to create like this. Once I could move it all to the latest version of Access (including the backend) the weekly corruption of the backend stopped, and the frontends had a dramatic performance increase.
 
Kraeg,

I would have to question if you had more issues than Access 97 as your backend. Perhaps you had a corrupt backend to start with.

I have at least 10 different companies with well over 100 users running this combination and it works fine. Second, I work with an accounting package that also works in this fashion and it also performs correctly. There are possibly several thousand end users working accross access versions with no problem in performance and none of the corruption issues that you experienced.

If you use the backend as intended, only tables, then this concept is A-Ok.

Sorry to disagree, but one bad experience does not make it a bad concept.

Hap

Access Add-on developer [pc] - [americanflag]
 
Oh, I know one bad experience doesn't make it all bad..... I was just relating what I had been through. I rebuilt the 97 backend various ways to try and stop the corruption problem, but it never helped.

I have another system that is a 97 backend to mixed frontends, and that hasn't become corrupt in well over a year. Although it also definitely appears to have performance drops (I've tested the 2002 frontends connected to a 2002 backend instead of the 97 backend and they definitely performed better).

Both these systems are in the same company, and based on that company's networking I wouldn't be surprised if it had more to do with the network setup.

I still prefer working with the one version if possible, but like most I am at the mercy of upgrade budgets.
 
What about if I built a A2000 application with FE/BE that now needs to be reduced to run on A97 since because of budget constraints.

Should I have much trouble moving them to A97?

Is there a reason to keep BE A2000 and just change FE?

What other things do I need to keep in mind that I may be missing?

I'd appreciate any comments.
 
When converting MDBs with linked tables, I've found it's best to remove the links, do the conversion, then relink the tables.

When I have failed to do this, either the conversion fails, or it succeeds yet hides all database objects, or it won't show the database window at startup and tells me to upgrade to a newer version of Internet Explorer (even though I have the latest).

I can't say that this is the case in all scenarios though.
 
Dear educate889

No, you can not leave the backend in Access 2000.

Those users who have Access 2000 can link to an Access 97 backend with no problem, because Access 2000 was written by Microsoft after Access 97 and is aware of and supports previous Access versions

but....

Those users who have Access 97 can NOT link to an Access 2000 backend, because Access 97 was written by Microsoft before Access 2000 was created and is not aware of the New Access versions/format.

Hope This Helps,
Hap [2thumbsup]

Access Add-on developer [pc] - [americanflag]
 
Kraeg and Hap

How can I make it a A97 database? What are the steps that you might know?

One other problem is that I have some security on the db right now that I know might get in the way.

Any hints would be appreciated
 
Dear Educate889,

Assuming that you have an Access 2000 mdb that you want to convert to an Access 97 format:

Using Access 2000,
1) Open the mdb
2) Select Tools>DatabaseUtilities>
3) Select Convert Database > To Prior Access Version

That should convert to an Access 97 database.
Note: Always Make a backup copy of the mdb before doing anything like converting.

Hope This Helps,
Hap [2thumbsup]


Access Add-on developer [pc] - [americanflag]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top