Don't know what you need. I'm using the code I downloaded to create/modify
the tables. I found that once the code had run it did not append to the
table that recorded the latest ID of the table modifications therefore when
the code ran it tried to recreate a table that already existed - alwasy
starting at 1. I then added my own code to check if record count was 0 - if
so add new record then use the ID as the value. Once the value had been
entered into the upgrade progress table the original code worked (if dcount
>0). However, to improve upgrades in the future how do I determine if a
>Don't know what you need. I'm using the code I downloaded to create/modify
>the tables.
"The" code. What code? You haven't indicated where you downloaded it from, or
posted any of the code.
>I found that once the code had run it did not append to the
>table that recorded the latest ID of the table modifications therefore when
[quoted text clipped - 4 lines]
>>0). However, to improve upgrades in the future how do I determine if a
>table exists before VBA tries to create it?
Again, Jason: you are not the only person posting to this newsgroup. Maybe you
have posted your code, a description of your table structure, and what
specific opreations you're trying to carry out... but I'm sorry, as an unpaid
volunteer I really don't have time or interest to Google search for all your
prior postings.
If you post a SPECIFIC question, *with code and a description of your tables*,
I or another volunteer will be glad to try to help. But please reread the
above with the assuimption that what you posted is *all* the information
available to someone trying to help: someone who does not know your business,
the structure of your tables, or the content of your code. Not much to go on,
eh?

Signature
John W. Vinson [MVP]
Jason - 04 May 2008 05:49 GMT
I shall repost:
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%20U
tility.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" <JAllenNZ@hotmail.com>
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,
[quoted text clipped - 78 lines]
> the structure of your tables, or the content of your code. Not much to go on,
> eh?