Conversion 2010 to 2003

[accessuser99]

I have made a fairly big Access 2010 database for a small community. Now they want me to convert it to Libre Office, but it only accepts mdb files (Access 2003 or 2000).

I got the message it could not convert because there are functions used which do not allow the conversion. I read about all the incompatible functions, and tried to simplify the database as much as possible. But still the message comes that it cannot convert because some functions still exist.

Glad if anyone could help...

 

[boblarson]

Try creating a new, blank 2002-2003 file format mdb file (you may have to go into the FILE > ACCESS OPTIONS to change the default format first. And then IMPORT everything from the 2010 version to the new mdb file. It will leave out any incompatible stuff.

 

[accessuser99]

Try creating a new, blank 2002-2003 file format mdb file (you may have to go into the FILE > ACCESS OPTIONS to change the default format first. And then IMPORT everything from the 2010 version to the new mdb file. It will leave out any incompatible stuff.

Thank you very much! I'll try that tomorrow.

 

[accessuser99]

Tried your suggestion and it worked! Thank you.
I could create an mdb file (Access 2003 compatible).
But I can't get it into Libre Office's Base.
This is probably not the forum for this. I've asked in two Libre Office forums and haven't got any reply yet.
Don't suppose anybody here have some tips, even though this may be the wrong place to ask?

 

[mdlueck]

This is probably not the forum for this. I've asked in two Libre Office forums and haven't got any reply yet.
Don't suppose anybody here have some tips, even though this may be the wrong place to ask?

I am interested in seeing how LibreBase compares to Borland Paradox and MS Access. I can find hardly anything on developing / programming DB applications with LibreBase. At one time I came across some reference that there exists a BASIC interpreter for the suite... just not sure of its capabilities... like is it GW BASIC grade, or is it Object-Oriented like VBA, or or or... TBD when I have time...

 

[Pat Hartman]

What was the purpose of converting to Libre Office? Are you aware that the runtime engine for MS Access is free and can be downloaded from the MS download site? This will allow users to run the database you developed without having to purchase Access licenses. You only need a full Access version on computers where someone will be doing development. ie creating forms/reports/queries etc. Everyone else just runs a database created by the developer.

 

[accessuser99]

What was the purpose of converting to Libre Office? Are you aware that the runtime engine for MS Access is free and can be downloaded from the MS download site? This will allow users to run the database you developed without having to purchase Access licenses. You only need a full Access version on computers where someone will be doing development. ie creating forms/reports/queries etc. Everyone else just runs a database created by the developer.

No, I was not aware of that. So, thank you!
The purpose of converting was exactly that the users could avoid buying a license.
So I'll try finding the download.

 

[accessuser99]

Found the download. Thanks again!

I have a dumb question. The MS instructions are very short.
When I have the full Access 2010 installed (on Windows 7, 64 bit), can or should I install the runtime module (x32) on my computer to "package" it with the application?
Or should the end-users just download or receive the runtime module (x32 I think but possibly also x64), and then open the application from it?

Another question - suppose after installing the runtime module on the end-users computers - they want some design changes, and they have made changes to the data. Will I need their updated database before the design changes are made? Or how would you else integrate the two?

 

[rodmc]

If we ever perfect cloning I think we shoud start cloning the likes of Bob, Pat, vbaInet etc, then we can all have one each

 

[boblarson]

Found the download. Thanks again!

I have a dumb question. The MS instructions are very short.
When I have the full Access 2010 installed (on Windows 7, 64 bit), can or should I install the runtime module (x32) on my computer to "package" it with the application?

No, you don't install it when you have the full version installed. When packaging, you should be able to select support files and that would be one.

Or should the end-users just download or receive the runtime module (x32 I think but possibly also x64), and then open the application from it?

That is possible too. But don't have them install the 64 bit version unless you are using 64 bit Office yourself.

Another question - suppose after installing the runtime module on the end-users computers - they want some design changes, and they have made changes to the data. Will I need their updated database before the design changes are made? Or how would you else integrate the two?

That can be a problem. Sometimes made easier by splitting the database (which should be done anyway) because then if most changes are to the frontend you can just send them a new frontend. If you need to make backend table changes that gets a little more challenging depending on what you need done and is why I came up with my Backend Auto Update tool (it doesn't do everything but it does a fair amount).

You can find that on my website in the Free Access Tools section (see my link in my signature).

 

[boblarson]

If we ever perfect cloning I think we shoud start cloning the likes of Bob, Pat, vbaInet etc, then we can all have one each