If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Installing updates to my app without losing the data
I have MS Access 2003 and MS Access 2003 Developer Extension and everything
else that came with Visual Studio Tools. I have deployed a simple database application using the Package Wizard and including Access Runtime. Now I am getting requests for changes. These changes will probably add new tables and add fields to existing tables. And there will certainly be new forms, queries and reports. How can I package my revised version of this application and install it easily without overwriting all the data that has already been entered? |
#2
|
|||
|
|||
Updating the code, forms, reports, and fixing bugs etc, and then sending
those updates is easy. I can't imagine you gotten so far as to using the developer tools and not yet have split you database? Just the general development process is VERY difficult when your database is not split. Further, your end users should get a mde for the program part. The data part can remain a mdb...it don't matter. So, with a split database, I often just send the client a zipped file (I use www.winzip.com). Or, you can even use the package wizard to include JUST your front end...and NOT include the runtime. This works well if you have to send them a cd. (but, email is usually much easier). You can read about splitting he http://www.granite.ab.ca/access/splitapp.htm Now, the above solves the problem of sending update for the program part (forms, reports, code fixes etc can all be updated with a simply file copy this way). however, to update the back end, that is more difficult. You either have to: a) have the client send you the back end...you modify it..and send it back. During this time, they can NOT add/edit data to the application. b) write code in your startup routines to "check" the version of the back end data file, and then if "old"version you then run some of your code to modify the tables. In other words, you use code, or sql "ddl" commands (alter table etc) to add new fields etc. to the back end. Writing this kind of code can be a bit of work. -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada http://www.attcanada.net/~kallal.msn |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Losing Saved data | Brian Ramsey | General Discussion | 3 | September 17th, 2004 12:30 AM |
Is this possible with Excel Chart? | q582gmzhi | Charts and Charting | 1 | September 8th, 2004 03:33 AM |
Losing data | plewiston | Database Design | 3 | July 12th, 2004 09:42 PM |
Problems with converting data held in an Excel spreadsheet to Word | mark Gray | Mailmerge | 6 | July 8th, 2004 10:54 AM |
Struggling with MS Query... | Alex | General Discussion | 5 | July 6th, 2004 11:46 AM |