HELP! How do I broadcast my fixes to all the installations of my Database?

[TakinANapster]

I have a 2010 Database written for free for the general public and have several users already BETA testing it.



It is almost ready to stamp a version on it and call it ready for production, but I have one huge problem!

How do I apply maintenance on a large scale? I've been having them email me their Database, then export to their Database the changes I made, then email them back the updated copy. This works OK with a limited number of BETA testers, however I expect possibly hundreds of users of this FREE Database.

When I come out with fixes, or a new version, how can I easily push out new code or have the users download and install the new code without wiping out their tables?

Please HELP!

Thanks in advance!!!

-Joe

[Toyman]

I have a 2010 Database written for free for the general public and have several users already BETA testing it.

It is almost ready to stamp a version on it and call it ready for production, but I have one huge problem!

How do I apply maintenance on a large scale? I've been having them email me their Database, then export to their Database the changes I made, then email them back the updated copy. This works OK with a limited number of BETA testers, however I expect possibly hundreds of users of this FREE Database.

When I come out with fixes, or a new version, how can I easily push out new code or have the users download and install the new code without wiping out their tables?

Please HELP!

Thanks in advance!!!

-Joe

You should always split your db into frontend and backend even if both parts resides in the same folder. The backend serves nothing more than a storage unit for the data. The front end is actually the work hourse containing all the forms, reports and codes. When you have to update the codes, you users simply have to replace the frontend with the new version

[TakinANapster]

You should always split your db into frontend and backend even if both parts resides in the same folder. The backend serves nothing more than a storage unit for the data. The front end is actually the work hourse containing all the forms, reports and codes. When you have to update the codes, you users simply have to replace the frontend with the new version

Thanks for the quick reply Toyman!!!

I'm somewhat of a newbie to Access. I know Programming in a lot of other languages, but Access only about 5 months under my belt.

My question is, front-end and back-end .... do you mean have two Databases? One that just has Tables, and the other to have Queries, Forms, Macros, etc.?

Would I somehow link the forms, queries, macros, etc. to the 2nd database to have access to the data? If so, could you steer me in the right direction to do reading on that subject?

Thanks in advance (again),

Joe

[Toyman]

Thanks for the quick reply Toyman!!!

I'm somewhat of a newbie to Access. I know Programming in a lot of other languages, but Access only about 5 months under my belt.

My question is, front-end and back-end .... do you mean have two Databases? One that just has Tables, and the other to have Queries, Forms, Macros, etc.?

Would I somehow link the forms, queries, macros, etc. to the 2nd database to have access to the data? If so, could you steer me in the right direction to do reading on that subject?

Thanks in advance (again),

Joe

Yes, the backend contains the actual tables. You will create link tables in your frontend which links to the tables in the backend. You will then write your codes and queries in the frontend refering to the linked tables in the frontend. This way, you can always swap out your frontend without wiping out all of the data in the tables because the frontend only contains link tables

[TakinANapster]

Yes, the backend contains the actual tables. You will create link tables in your frontend which links to the tables in the backend. You will then write your codes and queries in the frontend refering to the linked tables in the frontend. This way, you can always swap out your frontend without wiping out all of the data in the tables because the frontend only contains link tables

Thank you so VERY much!