How can I Position the Mouse Pointer? (A2003)

Jason,

You can update the Front-End file easily by sending the client a new
version. However, if you will need to make changes to the Back-End
file you need a different method. Assuming that you cannot visit each
client to make the necessary changes you need to add some code to the
Front-End which will make the relevant changes to the Back-End files
automatically.

There is code at this site :-
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE%20Update%20Utilit y.mdb'
which will do that for you. Just import the form, table and code
module into your database, add one line of code to your 'start up'
form and you are done. To add a new table or field to the Back-End you
just call up the BE Update form, enter the details of the table,
field, relationship, etc and the Back-End file is updated without
affecting the client's existing data.

You will also need to add relinking code to relink the Front-End file
to the tables in the Back-End file. See this site to do that
automatically :-
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

There is full documentation on both sites to explain the procedure
fully.

HTH

Peter Hibbs.

On Thu, 1 May 2008 18:58:18 +1200, "Jason"
wrote:

It is split as you say the tables in the user mde is for temporary data and
data i enter for look-ups etc. Since the data files have changed over time I
have found the process of copying and importing easier. Can you post an
example code where the table is checked and modified (i.e. fields added,
modified or deleted).

ALSO tables that are added

Thanks,
J
"Larry Linson" wrote in message
...
"Jason" wrote

How do I upgrade existing data? A database upgrade
i did involved copying the existing files using a batch
file, then copy the new files over the existing files then
a long routine in Access to import the old data into the
new tables.

Sounds as if you have not split your database into front end (queries,
forms, reports, macros, and modules) and back end (tables, data, and
relationships), with each user having a copy of the FE and the BE on a
shared folder.

-- The most common updates will be to the interface, so each user can
just
get
a new copy, because it does not store data (other than, perhaps,
some
rarely-
changing lookup tables -- state abbreviation and state name, for
example).

-- When you have to make a change in the data structure, the common
approach
(if you can't go to the location, and open the back end manually)
is
to
write
VBA code in DAO or ADO to modify the table design (if needed) and
data
in the shared back end, and update with any additional data that
you
are adding,
and have one user or administrator at the production site execute
that
when
they have exclusive access.

There's other information about splitting and about an Auto FE Updater
for
use in multiuser environments at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

Good luck with your projects.

Larry Linson
Microsoft Office Access MVP

I've got relinking sorted but will look at the other later to see if it's
woth doing.
"Peter Hibbs" wrote in message
...
Jason,

You can update the Front-End file easily by sending the client a new
version. However, if you will need to make changes to the Back-End
file you need a different method. Assuming that you cannot visit each
client to make the necessary changes you need to add some code to the
Front-End which will make the relevant changes to the Back-End files
automatically.

There is code at this site :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE%20Update%20Utilit y.mdb'
which will do that for you. Just import the form, table and code
module into your database, add one line of code to your 'start up'
form and you are done. To add a new table or field to the Back-End you
just call up the BE Update form, enter the details of the table,
field, relationship, etc and the Back-End file is updated without
affecting the client's existing data.

You will also need to add relinking code to relink the Front-End file
to the tables in the Back-End file. See this site to do that
automatically :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

There is full documentation on both sites to explain the procedure
fully.

HTH

Peter Hibbs.

On Thu, 1 May 2008 18:58:18 +1200, "Jason"
wrote:

It is split as you say the tables in the user mde is for temporary data
and
data i enter for look-ups etc. Since the data files have changed over
time I
have found the process of copying and importing easier. Can you post an
example code where the table is checked and modified (i.e. fields added,
modified or deleted).

ALSO tables that are added

Thanks,
J
"Larry Linson" wrote in message
...
"Jason" wrote

How do I upgrade existing data? A database upgrade
i did involved copying the existing files using a batch
file, then copy the new files over the existing files then
a long routine in Access to import the old data into the
new tables.

Sounds as if you have not split your database into front end
(queries,
forms, reports, macros, and modules) and back end (tables, data, and
relationships), with each user having a copy of the FE and the BE on
a
shared folder.

-- The most common updates will be to the interface, so each user
can
just
get
a new copy, because it does not store data (other than, perhaps,
some
rarely-
changing lookup tables -- state abbreviation and state name, for
example).

-- When you have to make a change in the data structure, the common
approach
(if you can't go to the location, and open the back end
manually)
is
to
write
VBA code in DAO or ADO to modify the table design (if needed)
and
data
in the shared back end, and update with any additional data
that
you
are adding,
and have one user or administrator at the production site
execute
that
when
they have exclusive access.

There's other information about splitting and about an Auto FE
Updater
for
use in multiuser environments at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

Good luck with your projects.

Larry Linson
Microsoft Office Access MVP

I get error "Can't find input table "TableName""
"Peter Hibbs" wrote in message
...
Jason,

You can update the Front-End file easily by sending the client a new
version. However, if you will need to make changes to the Back-End
file you need a different method. Assuming that you cannot visit each
client to make the necessary changes you need to add some code to the
Front-End which will make the relevant changes to the Back-End files
automatically.

There is code at this site :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE%20Update%20Utilit y.mdb'
which will do that for you. Just import the form, table and code
module into your database, add one line of code to your 'start up'
form and you are done. To add a new table or field to the Back-End you
just call up the BE Update form, enter the details of the table,
field, relationship, etc and the Back-End file is updated without
affecting the client's existing data.

You will also need to add relinking code to relink the Front-End file
to the tables in the Back-End file. See this site to do that
automatically :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

There is full documentation on both sites to explain the procedure
fully.

HTH

Peter Hibbs.

On Thu, 1 May 2008 18:58:18 +1200, "Jason"
wrote:

It is split as you say the tables in the user mde is for temporary data
and
data i enter for look-ups etc. Since the data files have changed over
time I
have found the process of copying and importing easier. Can you post an
example code where the table is checked and modified (i.e. fields added,
modified or deleted).

ALSO tables that are added

Thanks,
J
"Larry Linson" wrote in message
...
"Jason" wrote

How do I upgrade existing data? A database upgrade
i did involved copying the existing files using a batch
file, then copy the new files over the existing files then
a long routine in Access to import the old data into the
new tables.

Sounds as if you have not split your database into front end
(queries,
forms, reports, macros, and modules) and back end (tables, data, and
relationships), with each user having a copy of the FE and the BE on
a
shared folder.

-- The most common updates will be to the interface, so each user
can
just
get
a new copy, because it does not store data (other than, perhaps,
some
rarely-
changing lookup tables -- state abbreviation and state name, for
example).

-- When you have to make a change in the data structure, the common
approach
(if you can't go to the location, and open the back end
manually)
is
to
write
VBA code in DAO or ADO to modify the table design (if needed)
and
data
in the shared back end, and update with any additional data
that
you
are adding,
and have one user or administrator at the production site
execute
that
when
they have exclusive access.

There's other information about splitting and about an Auto FE
Updater
for
use in multiuser environments at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

Good luck with your projects.

Larry Linson
Microsoft Office Access MVP