Access 97 vs XP

I would like to know if I convert Access 97 Prod to XP prod, what kind
of problems I am going to have. Please highlight the points in general.
I heard that Macros do not work if converted to XP??

Thanks a lot
Param




*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

re: Access 97 vs XP

"Param" <param_pek@yahoo.com> wrote in message
news:40d05753$0$25469$c397aba@news.newsgroups.ws.. .[color=blue]
> I would like to know if I convert Access 97 Prod to XP prod, what kind
> of problems I am going to have. Please highlight the points in general.
> I heard that Macros do not work if converted to XP??[/color]

Generally speaking, if an Access 97 file is error and corruption free it
should convert to any of the newer versions and work properly. A good test
is to see if you can successfully create an MDE from the 97 file before
attempting the conversion.

I have not heard the macro issue prior to your post, but I can't say for
sure whether it is untrue or not. I would be very surprised if that is the
case though.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

re: Access 97 vs XP

Thanks for the reply. Actually, I have the app. on Access 97, where as
my company is putting XP to all machines. But, we would like to hold on
to those people who have access to the apps, which is on Access97. The
administrator is telling me that it is not a good idea to open the
Access97 apps. on XP, that will corrept the application. I don't know
how far it is true?

Second and last question:
Is any other things you can think of moving the Access 97 application to
XP??

thanks again for your help
Param


*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

re: Access 97 vs XP

"Param" <param_pek@yahoo.com> wrote in message
news:40d0863a$0$25482$c397aba@news.newsgroups.ws.. .[color=blue]
>
> Thanks for the reply. Actually, I have the app. on Access 97, where as
> my company is putting XP to all machines. But, we would like to hold on
> to those people who have access to the apps, which is on Access97. The
> administrator is telling me that it is not a good idea to open the
> Access97 apps. on XP, that will corrept the application. I don't know
> how far it is true?[/color]

When the XP users open the file they will be asked if they want to convert
it or open it. They have to choose "open" if you still want people with
A97 to use the file. However; the XP users (after they choose open) will
not be able to make any design changes to any objects. They should be able
to edit and enter data though.

The "open" process does still modify the file, just not to the same extent
as if it was converted. I have not heard of any reports of that leading to
file corruption. However; having multiple users open the same front end
file is always a corruption risk regardless of versioning issues so if that
is what you are doing, then you are running a risk, and that risk is much
higher with versions later than A97.



--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

re: Access 97 vs XP

Param <param_pek@yahoo.com> wrote:
[color=blue]
>I would like to know if I convert Access 97 Prod to XP prod, what kind
>of problems I am going to have. Please highlight the points in general.
>I heard that Macros do not work if converted to XP??[/color]

I've never heard that macros won't work so I very much doubt it.

Access 2.0 and Access 97 to Access 2000/2002 conversion problems
http://www.granite.ab.ca/access/conversionproblems.htm

As Rick points out your apps should be split into a FE/BE. The A2003 users can use
the A2003 FE but continue to use an A97 BE until all the users are converted. This
can make for a smoother transition.

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
http://www.granite.ab.ca/access/splitapp/ for more info. See the Auto FE Updater
downloads page http://www.granite.ab.ca/access/autofe.htm 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

re: Access 97 vs XP

Thanks Tony and Rick for the reply. I will get back to you if I have
any other questions.

Again thank Q and have a good weekend
Param


*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!