Converting to Standalone

[Geoffk]

Hi All

I am currently compiling an Access DB to manage my work in progress, Payments due etc.

The DB is starting to work well and have requests from fellow contractors to purchase a copy (there are over 400 subcontractors in the group), with this in mind I have decided that when I complete the DB I will take it to a proffessional programmer and have it converted to a fully standalone programm.

My question: Is there a programm format that is preferable or would C# be the best option or is there a product out there that I could purchase and use.

Thanks in Advance
GeoffK

 

[boblarson]

You can not create an executable of an Access database. However, you have a few options:

1. Create an MDE file and let users use that, but they would need Access to do so (except with Option 2). They can open tables and queries, but can't open forms, reports, macros, or modules in design view.

2. Create and MDE file and use the developer's edition of Access to create an install file to install the runtime version of Access so that they can run your MDB file. See more about that here: http://www.access-programmers.co.uk/forums/showthread.php?s=&postid=226180#post226180 (if using Access 2007, there is no runtime yet, but they are supposed to be coming out with it anytime and it should be free, unlike previous versions)

3. Create a frontend from another program (C++, C#, VB, etc.) to access the data in the tables and queries. But, you can't use forms and reports from Access this way. You would need to build everything yourself in your programming language.

 

[KeithG]

If you going to sell this db I would make sure your data is properly normalized. You don't want to be selling a BS product (no offense).

 

[Banana]

Some notes:

1) There are indeed products out that claims to convert Access to .NET environment. However, they will break more than they convert.

2) By far biggest benefit of using Access over a standalone .exe is this: Rapid development cycles. A year later, someone need to track new information. In Access, you add the necessary fields or tables, update a form's recordsource, and drag'n'drop the new control bound to the forms. Pesto! You're done!

With a standalone exe, you need to add the necessary fields/tables, update the bindings, add the control to the form, then bind it to the new field, and update the code managing the load/save of the data retrieved and re-written. Basically, lot more steps you have to perform manually to get it working.

3) If you still want a standalone app, I'd probably consider using PHP or some kind of web language for rapid deployment. (Note I said deployment, not development). This will at least help simplify the support as you don't need to worry about if a .exe will work on anybody's computer.

HTH.