Datatypes Coversion Issues

[raghuramraichooti]

Hi,
I am trying to convert the Access 97 to Access 2003 and the problem is that,
there might be many changes in the datatypes. i want to know the details of
them.

eg: An int can be converted to String but string cant be converted to Int.

In this way i want to know the other issues.
Some might ask me why do i require???? When i am converting or merging the
DB, to handle the issues raised.

Can any one help me out. . .. ..

 

[privatenews]

Hello Raghuram,

The following are some known issues when converting Access 97 database to
2003

887032 You may receive an error message when you try to convert a Microsoft
Access 2000 or a later version database to a Microsoft Access 97 database
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887032

310937 Cannot open or convert an Access 97 or Access 2000 database in
Access 2002 or Access 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;310937

You may want to review the following thread for another issue:
http://groups.google.com/group/microsoft.public.access.queries/browse_frm/th
read/efeb09071bae8b5e/e71191f3be1329d6?tvc=1#e71191f3be1329d6

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================


This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------

 

[Allen Browne]

If you have already built a database in Access 97, you should not need to
change any of the field types, nor any of the VBA code types in order to
convert it to Access 2003. Access 2003 supports all the same field types,
and all the same VBA types.

If you already have a problem with your A97 database, you will probably have
the same problems after you convert.

It is also possible that some of calculated fields that worked in Access 97
queries will not work correctly in Access 2003, as JET 4 (the data engine in
Access 2003) is not as good as JET 3.5 (the A97 data engine) at interpreting
calculated fields. If you are facing this issue, you can explicitly typecast
the calculations to solve the problem. Details on how to do that in:
Calculated fields misinterpreted
at:
http://allenbrowne.com/ser-45.html

For a list of other issues you may need to be aware of, see:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://allenbrowne.com/ser-48.html

 

[jxsq]

尊敬的大虾：
您好ï¼
以åŽæ”¹ç”¨ä¸­æ–‡å†™æ¶ˆæ¯å¥½å—？