Converting Access 97 to 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello to all -- I have been out of the loop for a while and was wondering if
anyone has converted old Access 97 over to Access 2003 and if you experienced
any problems use it under the new system? Thanks in advance for input. NewB
 
ADB-NewB said:
Hello to all -- I have been out of the loop for a while and was wondering
if
anyone has converted old Access 97 over to Access 2003 and if you
experienced
any problems use it under the new system? Thanks in advance for input.
NewB
Click to expand...

Remarkably few.

Access 2000 and later versions have a weird habit of bloating frontends,
even if they contain no local tables (only linked tables). They seem to hit
a certain size and then the bloat stops. I don;t recall A97 ever having this
issue.

Other than that nothing really springs to mind. The conversion process for
Access systems has always been very smooth for me.

If you have any specific problems whilst converting there are certainly
plenty of people here who will have experienced the same problem already and
will have a solution.

Ed Metcalfe.
 
Thanks for your bloating responce however, I'm not familar with that term can
you explain?
 
Frontend MDB file growing in size, even though it contains no data...

Ed Metcalfe.
 
Ed Metcalfe said:
Remarkably few.
Click to expand...

I'd agree with that.
Access 2000 and later versions have a weird habit of bloating frontends,
even if they contain no local tables (only linked tables). They seem to hit
a certain size and then the bloat stops. I don;t recall A97 ever having this
issue.
Click to expand...

A97 would bloat the FE's too. Even if they were MDEs.

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
 
SQL Server has 'bloat also'

but of course, you can bounce the service which resets the TempDb..
and you can autoshrink the files.. by default that is on..

and of course, you can setup a 'database maintenance plan' in order to
automate shrinking the db-- on a scheduled basis

it takes no code; and it is infinitely more dependable than writing a
batch file to launch Access

hope that helps

MDB is for lamers
 
Back
Top