I am new to Access development and have read through Beginning Access 2000 VBA book before developing 

my first application in Access2000/DAO.  This application is in use and now I am making some 

enhancements and bug fixes.  My questions are:



1- Is there a tool to keep track of application changes?

2- How does one deliver an updated application (table structure, relationships, module code, form & 

report changes) without over-writing data in existing database?



Please point me in the right direction if this is not the forum for such questions.



Thanks.



Malcolm

Hi Malcolm,



To deliver an updated application without over-writing data in existing 

database you should have designed your application with ease of maintenance

 in mind (front-end database to store you application part/back-end 

database to store your data tables.)



You will find it hard to maintain you code and other front-end components, 

such as reports, forms, queries, etc, if you stored both your data and 

code in one database.



If everything is one database, you may have to manually split your 

application (front-end/back-end components) or use the wizard to do it for 

you (Tools, Add-Ins, Database Splitter) so it becomes easy to maintain now 

and later down the truck.



Hope that helps





_____________________________________



John Fejsa

Systems Analyst/Computer Programmer

Hunter Centre for Health Advancement

Locked Bag 10

WALLSEND NSW 2287

Phone: (02) 49246 336 Fax: (02) 49246 209

________________________________________





I am new to Access development and have read through Beginning Access 2000 

VBA book before developing

my first application in Access2000/DAO.  This application is in use and 

now I am making some

enhancements and bug fixes.  My questions are:



1- Is there a tool to keep track of application changes?

2- How does one deliver an updated application (table structure, relationsh

ips, module code, form &

report changes) without over-writing data in existing database?



Please point me in the right direction if this is not the forum for such 

questions.



Thanks.



Malcolm

The application is split in front-end/back-end but when I try to import data from production 

database to the updated back-end, I don't see a way of importing data only and not the structure.  

Normally I should be able to use the back-end as is but sometimes I make a change in table structure 

and need to migrate data. 



I  must be missing something very obvious since import does not offer this option.



Thanks for your assistance.



> Hi Malcolm,

> 

> To deliver an updated application without over-writing data in existing 

> database you should have designed your application with ease of 

maintenance

>  in mind (front-end database to store you application part/back-end 

> database to store your data tables.)

> 

> You will find it hard to maintain you code and other front-end 

components, 

> such as reports, forms, queries, etc, if you stored both your data and 

> code in one database.

> 

> If everything is one database, you may have to manually split your 

> application (front-end/back-end components) or use the wizard to do it 

for 

> you (Tools, Add-Ins, Database Splitter) so it becomes easy to maintain 

now 

> and later down the truck.

> 

> Hope that helps

> 

> 

> _____________________________________

> 

> John Fejsa

> Systems Analyst/Computer Programmer

> Hunter Centre for Health Advancement

> Locked Bag 10

> WALLSEND NSW 2287

> Phone: (02) 49246 336 Fax: (02) 49246 209

> ________________________________________

> 

> 

> I am new to Access development and have read through Beginning Access 

2000 

> VBA book before developing

> my first application in Access2000/DAO.  This application is in use and 

> now I am making some

> enhancements and bug fixes.  My questions are:

> 

> 1- Is there a tool to keep track of application changes?

> 2- How does one deliver an updated application (table structure, 

relationsh

> ips, module code, form &

> report changes) without over-writing data in existing database?

> 

> Please point me in the right direction if this is not the forum for such 



> questions.

> 

> Thanks.

> 

> Malcolm

> 

You could use an append query to import data from your old database to 

updated database or just copy the data individual tables.



Depending on the number of changes you made to the new version, you may 

have to change your select query to reflect format changes, ie.,, you may 

have to add new columns to the query to mimic the new version  before you 

can copy the data.



For instance, if you old table had the following fields: name, address, 

sex and you new table added a new field called title your query would have 

the following fields: Title:"", Name, Address, Sex. The new Title field 

would contain null value, however, the query would mimic the structure of 

the new database table and you could copy the old database table to the 

new one.



I hope that makes sense





_____________________________________



John Fejsa

Systems Analyst/Computer Programmer

Hunter Centre for Health Advancement

Locked Bag 10

WALLSEND NSW 2287

Phone: (02) 49246 336 Fax: (02) 49246 209

________________________________________



CONFIDENTIALITY & PRIVILEGE NOTICE

The information contained in this email message is intended for the named 

addressee only.  If you are not the intended recipient you must not copy, 

distribute, take any action reliant on, or disclose any details of the 

information in this email to any other person or organisation.  If you 

have received this email in error please notify us immediately.



>>> rmk9785e@h... 15/05/2001 14:51:41 >>>

The application is split in front-end/back-end but when I try to import 

data from production

database to the updated back-end, I don't see a way of importing data only 

and not the structure. 

Normally I should be able to use the back-end as is but sometimes I make a 

change in table structure

and need to migrate data.



I  must be missing something very obvious since import does not offer this 

option.



Thanks for your assistance.



> Hi Malcolm,

>

> To deliver an updated application without over-writing data in existing 

=3D

> database you should have designed your application with ease of

maintenance=3D

>  in mind (front-end database to store you application part/back-end =3D

> database to store your data tables.)=3D20

>

> You will find it hard to maintain you code and other front-end

components, =3D

> such as reports, forms, queries, etc, if you stored both your data and 

=3D

> code in one database.=3D20

>

> If everything is one database, you may have to manually split your =3D

> application (front-end/back-end components) or use the wizard to do 

it

for =3D

> you (Tools, Add-Ins, Database Splitter) so it becomes easy to maintain=20



now =3D

> and later down the truck.=3D20

>

> Hope that helps

>

>

> _____________________________________

>

> John Fejsa

> Systems Analyst/Computer Programmer

> Hunter Centre for Health Advancement

> Locked Bag 10

> WALLSEND NSW 2287

> Phone: (02) 49246 336 Fax: (02) 49246 209

> ________________________________________

>

>

> I am new to Access development and have read through Beginning Access

2000 =3D

> VBA book before developing=3D20

> my first application in Access2000/DAO.  This application is in use and 

=3D

> now I am making some=3D20

> enhancements and bug fixes.  My questions are:

>

> 1- Is there a tool to keep track of application changes?

> 2- How does one deliver an updated application (table structure,

relationsh=3D

> ips, module code, form &=3D20

> report changes) without over-writing data in existing database?

>

> Please point me in the right direction if this is not the forum for 

such

=3D

> questions.

>

> Thanks.

>

> Malcolm

>





.au






This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient,
please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily
the views of Hunter Health.