How to convert Access 1.x to access 2003 or 2010?

[jambai]

Hi,

How to convert Access 1.x to access 2003 or 2010?

I came across few forums and they suggested to do the following steps.
[ul]
[li]Use either A2 or A97 to convert from Access 1.0[/li]
[li]Use A2003 to convert from A2 or A97.[/li]
[li]When I am doing import(Open a blank 2003 Database and import from Access 1.x Database), the Macros and Modules are not importing. [/li][/ul]
In the net I am not able to find Access 2.0 download

Any help in this regard is highly appreciated

Thanks
Jambai

 

[kermit01de]

Hello Jambai,

long time ago I did some mdbs in A2.0 - indeed with VBA and macros. While trying to convert them "simply" to A97 I figured out, that some major things within (at least) VBA changed. Same thing in the newer versions. VBA ran into loops after converting etc etc etc

What I did: Having A2.0 in addition to newer versions on client machines to run the mdb. Otherwise it would have been to much work compared to number of users to convert all code.

So I assume you should think about create a new application. this is btw a great opportunity to cut off some stuff that may be crap ;-)

Regards
Mirko

Kind regards
Mirko
--------------------------------------
>>>>>> ... I am sure, some supportissues are a matter of PEBKAC ... <<<<<

 

[flyboytim]

I'm not sure that Microsoft has released early versions of Office and MS Office component apps from their original licenses as free unsupported software, like some old MS-DOS versions are, but they are available for download on this Russian Site:

http://www.vetusware.com/category/Office/?cat=4&page=4

http://www.vetusware.com/category/Office/?cat=4&page=5

and related pages.

Beware! - the Office versions 4.3 and earlier made for Windows 3.x - they do not support long filenames, or pathnames with spaces, so do not install them in "C:\Program Files", or store your documents in "C:\My Documents" etc.!

I still use Office 97 Professional - snappy loading, small footprint and small documents. I can always use free 3rd party converters for docx, etc., or print to PDF files using freeware utilities. I also know where everything I want to use in an office suite is! No nagging activation popups, yada yada yada...

http://www.fxxxingcomputers.co.uk

 

[flyboytim]

Should have said that when you incrementally change versions from 1->2->3 or whatever, it is a good idea to debug any code first or even copy it to a text file for analysis, then compact and repair the MDB in each version before conversion, and then test it as fully as you can after conversion. Also to get Access to document the databases and save the data dictionaries for comparison.

It helps if the data and code are split (if not already done) into front and back end mdbs as well, and to likewise process them. If any conversion breaks the functionality it is easier to figure out why that way.

http://www.fxxxingcomputers.co.uk

 

[jambai]

Thank you all for your feed back.

I've fixed the issue by importing Access 1.x's Forms, Macros, Modules and etc., into Access 2003. But the existing modules and macros needs to be changed as per latest DAO.

Below link will tells you the DAO object Library's compatibility

http://msdn.microsoft.com/en-us/library/aa190648(v=office.10).aspx

Thanks
Jambai