Which developer's kit?

[boxster]

Does it matter which Developer's kit I use to create a run-time version of an Access 97 database? Pros/Cons?

 

[Crilen007]

Ive noticed problems updating, and crashes on certain parts.. I hate the runtime thing, drove me nuts.

 

[boxster]

Yeah, I know, but otherwise I have to convert everything into VB code or something...

 

[Crilen007]

I dont know what you mean.

You want other people to use the DB without having access?

 

[boxster]

Exactly!

 

[Crilen007]

Well, last time i tried it, it didnt work out, however, some of the databases that were being used where quite complex. If yours is fairly simple it should work ok.

As for the developer kit, it should work ok with any, but I would use one meant for that version to be on the safe side.

 

[boxster]

OK, thank you very much...So, the only way to see is to try...

Do you know if it differs to first make an mde and then turn it into the run-time version or just convert the mdb file?

 

[Crilen007]

Stolen from Access help:

If your database contains Microsoft Visual Basic for Applications (VBA) code, saving your Microsoft Access database as an MDE file compiles all modules, removes all editable source code, and compacts the destination database. Your Visual Basic code will continue to run, but it cannot be viewed or edited. Saving your database as an MDE file secures you forms and reports without requiring users to log on or requiring you to create and manage the user accounts and permissions that are needed for user-level security.

Your database will continue to function normally—-you can still update data and run reports. Additionally, the size of the database will be reduced due to the removal of the code, so memory usage is optimized, which will improve performance.

Saving your Access database as an MDE file prevents the following actions:

Viewing, modifying, or creating forms, reports, or modules in Design view.
Adding, deleting, or changing references to object libraries or databases.
Changing code — an MDE file contains no source code.
Importing or exporting forms, reports, or modules. However, tables, queries, data access pages, and macros can be imported from or exported to non-MDE databases.

 

[boxster]

Thanks, I have read this before, but I wonder if converting the database into the run-time version provides the same properties as well.

So, why not just convert it from mdb to run-time rather than convert mdb into mde and then into run-time?

 

[Crilen007]

Smaller file size, faster, more secture, less chance of users messing something up.

 

[boxster]

Great, thanks! Then, I'll first create an mde and then convert it to the run-time version with ODE 97 if I can still find one around...

 

[Pat Hartman]

boxster,
There is no such thing as a runtime version of YOUR database. There is a runtime version of Micorsoft Access. To obtain a license to distribute the runtime version of Access, you must purchase the developer's edition. This DOES NOT IN ANY WAY change your database. The packaging and deployment wizard included with the developer's edition will create a self-extracting file that includes your UNMODIFIED database, the runtime version of Access, and whatever other support files that are necessary to run your database without having a full retail version of Access installed.

As to what version to use, always buy the newest version. Convert your database to the current version of Access, create an .mde file, and then create the distribution package. Since you are distributing Access along with your database, there is no upside to distributing an old version.

Be aware that running your app with the runtime version of Access will almost certainly require changes to your app to make it operate properly.