Multi-user A97 to AXP migration plan

[yankee428]

63 users, many locations. Not all users are going to XP at once. DB is not currently split and is in 97 format. My plan was to split DB and create two front ends, 97 and XP. Then, create a VB script that detects the local version of Access and launches the appropriate front end. This will avoid having the user choose the appropriate icon and possibly converting the 97 FE by accident. When everyone is on XP remove the VB script and 97FE.

Here is my question. What is my risk of corruption running an XP FE to a 97 BE.

Any feedback is appreciated.

 

[Crilen007]

I don't know what the risk of corruption is, however. I would say it would be easier to just have 2 front ends, and not have a program find out who has what.

It would be easier to just have two front ends, problem with that is, you will have to change both, when you change one.

Id say atleast get them upgraded to a newer version, either that or give them a runtime for access, so they dont evne need access installed.

 

[yankee428]

what is a runtime for access? How does that work?

 

[The_Doc_Man]

You need a developer's kit to get an Access run-time.

If I recall correctly, the b.e. DB is the same for A97 and later versions, but the f.e. is not. So you would need two front-ends. If the development process is not continuously ongoing, allow them to download the f.e. that corresponds to the DB they have. OR... work with your security manager to protect yourself. DISALLOW access to the downloadable copy of the f.e. based on your knowledge of the state of conversion. You could also do something stinky - like create ONE unique object in each f.e. - a form or table that is hidden and never gets used, but that some startup code can test. Disallow READ to those folks on Ac97 opening the XP version, and do the same in the other direction to the XP folks opening the Ac97 version.

Also, this is a case where user education is paramount. TELL them to avoid certain actions. Then carry a ruler. Smear it in chicken blood and tell them it is for their knuckles if they screw up. Adopt a Peter Lorre accent when you warn them. Leer a little bit and examine their knuckles. Make comments about "oh, such NICE knuckles..." But I digress.

 

[yankee428]

How do I get a developer's kit? Is there a cost? What is the official name of it?

Thanks for your help,

 

[The_Doc_Man]

Having reviewed your problem I'm not sure that's what you want. When I answered your question about the run-time, it was a follow-up on Crilen's comment, but I'm not sure I agree with him.

First, if you are serious about conversion, you would need a run-time for Ac97 and another for XP. Second, the runtime kit would only allow users to run existing queries, forms, reports. They could never "roll their own" query with it. If your users can build their own queries, it is NOT the solution.

However, since you asked, the name is similar to Office Standard or Office Professional. It would be Office Developer (or Access Developer) for the version you were seeking. You get a developer's kit at the same kind of store where you would get a copy of Office Professional or whatever. They might have to order one for you as it is not a commonly used item. Most of the time, Professional kits are good enough. And an Office 97 or Ac97 Developer's kit might no longer be available, so you would be on E-bay or one of the other sites that specialize in resale items.

I would advise having two f.e. copies based on what version of Office the user has on their workstation.