Access97 to XP migration / conversion???

  • Thread starter Thread starter Norman Fritag
  • Start date Start date
N

Norman Fritag

Hi,

I am looking information regarding Access97 to XP migration / conversion
issues ( other than Microsoft support pages)??

Can anyone point me into the right direction (webs) and or email me your
experience.

many thanks in advance

Norman
 
Norman said:
I am looking information regarding Access97 to XP migration / conversion
issues ( other than Microsoft support pages)??

Can anyone point me into the right direction (webs) and or email me your
experience.
Click to expand...

With one exception, the few apps that I converted took all
of about one minute each using the builtin feature.

Learning to use the new VBE environment was my biggest
stumbling block

The one problem I ran into was where I had some code that
used Me.Section(N).Controls.Count and that turned out to be
caused by a difference between Windows 9x and Windows NT/XP.

Check Tony Toews site, he has some notes on this subject:
http://www.granite.ab.ca/access/conversionproblems.htm
 
thanks
Marshall.

Marshall Barton said:
With one exception, the few apps that I converted took all
of about one minute each using the builtin feature.

Learning to use the new VBE environment was my biggest
stumbling block

The one problem I ran into was where I had some code that
used Me.Section(N).Controls.Count and that turned out to be
caused by a difference between Windows 9x and Windows NT/XP.

Check Tony Toews site, he has some notes on this subject:
http://www.granite.ab.ca/access/conversionproblems.htm
Click to expand...
 
Jet 4 is more tricky with Type Conversions (for example
numbers or nulls in date fields). The IISAMS seem to
work slightly differently (text/excel/dbf). Eval
and Run are slightly different. The Jet 2.5/3.5 conversion
layer is gone. Pipe symbols "|" in queries work differently.
Identity_Insert works differently with linked SQL Server
tables.

Note that these are all 'unusual' issues: expect similar
problems if are doing something else that edges on 'uncommon'.

Autonumbers no longer reset when you compact a database.
(later versions of Jet 4).

You may wish to turn off Autocorrect and SubDataSheets.

When converting to A2K we had to get rid of 'on error resume
next' in some places. We also had to remove deeply nested
VBA/DAO/UDF/DAO/UDF/DAO. We also had to add error handling
in some places where it was missing from nested VBA functions.

Access XP allows you to have many more objects in a
database than A97 did: we can fit all of our libraries
into one database.
 
Back
Top