Wrox Home  
Search P2P Archive for: Go

  Return to Index  

access thread: Synchronized only the structure changes


Message #1 by "George Oro" <george@c...> on Tue, 30 Jul 2002 19:12:41 +0400
Hi Guys,

What is the best approach to modify the db back-end on site (Customer Place) automatically without affecting the data?

What I mean is, the db is already installed on my customer place, the setup is, front-end on each client machine and back-end on the
server. Sometimes I need to change something on the back-end tables, let say I add some fields. What I used to do is do the changes
here in the office to test and do the same on the customer place (double job), because if I just copy and overwrite, they will loss
their data.

What I want is to synchronized only the structure, is there any way to automate this?


Any idea or help is highly appreciated.


Cheers,
George


Message #2 by PStreeter@C... on Tue, 30 Jul 2002 15:16:35 CST
I have seen pieces of VBA code to open a table for 
design, add new fields, save and close it. I do not yet 
have the VBA prowess to write an example, but maybe 
someone will do that or even point you to an example 
in a book (with a CD to plagiarize)

Paul

On Tue, 30 Jul 2002 19:12:41 +0400 "George Oro" wrote:

> Hi Guys,
> 
> What is the best approach to modify the db back-end on site (Customer 
> Place) automatically without affecting the data?
> 
> What I mean is, the db is already installed on my customer place, the 
> setup is, front-end on each client machine and back-end on the
> server. Sometimes I need to change something on the back-end tables,
> let say I add some fields. What I used to do is do the changes
> here in the office to test and do the same on the customer place
> (double job), because if I just copy and overwrite, they will loss
> their data.
> 
> What I want is to synchronized only the structure, is there any way
> to automate this?
>


Message #3 by "Wesley Kendrick" <wez.k@n...> on Tue, 30 Jul 2002 22:29:42 +0100
What about creating a make-table query which creates an (empty) table with
the new fields incorporated, then using an append query to write the data
from the old table into the new table. You can then delete the old table and
rename the new table with the old name.

regards, Wesley Kendrick

----- Original Message -----
From: <PStreeter@C...>
To: "Access" <access@p...>
Sent: Tuesday, July 30, 2002 10:16 PM
Subject: [access] Re: Synchronized only the structure changes


> I have seen pieces of VBA code to open a table for
> design, add new fields, save and close it. I do not yet
> have the VBA prowess to write an example, but maybe
> someone will do that or even point you to an example
> in a book (with a CD to plagiarize)
>
> Paul
>
> On Tue, 30 Jul 2002 19:12:41 +0400 "George Oro" wrote:
>
> > Hi Guys,
> >
> > What is the best approach to modify the db back-end on site (Customer
> > Place) automatically without affecting the data?
> >
> > What I mean is, the db is already installed on my customer place, the
> > setup is, front-end on each client machine and back-end on the
> > server. Sometimes I need to change something on the back-end tables,
> > let say I add some fields. What I used to do is do the changes
> > here in the office to test and do the same on the customer place
> > (double job), because if I just copy and overwrite, they will loss
> > their data.
> >
> > What I want is to synchronized only the structure, is there any way
> > to automate this?
> >
>
>
>
>

Message #4 by Paul Streeter <PStreeter@C...> on Tue, 30 Jul 2002 20:48:02 -0500
Wesley, are you remembering that he has to supply a macro or subroutine 
in the front end MDE file to do this to the back end MDB at the 
customer's site without his intervention?

Paul

Wesley Kendrick wrote:
> What about creating a make-table query which creates an (empty) table with
> the new fields incorporated, then using an append query to write the data
> from the old table into the new table. You can then delete the old table and
> rename the new table with the old name.
> 
> regards, Wesley Kendrick
> 
> ----- Original Message -----
> From: <PStreeter@C...>
> To: "Access" <access@p...>
> Sent: Tuesday, July 30, 2002 10:16 PM
> Subject: [access] Re: Synchronized only the structure changes
> 
> 
> 
>>I have seen pieces of VBA code to open a table for
>>design, add new fields, save and close it. I do not yet
>>have the VBA prowess to write an example, but maybe
>>someone will do that or even point you to an example
>>in a book (with a CD to plagiarize)
>>
>>Paul
>>
>>On Tue, 30 Jul 2002 19:12:41 +0400 "George Oro" wrote:
>>
>>
>>>Hi Guys,
>>>
>>>What is the best approach to modify the db back-end on site (Customer
>>>Place) automatically without affecting the data?
>>>
>>>What I mean is, the db is already installed on my customer place, the
>>>setup is, front-end on each client machine and back-end on the
>>>server. Sometimes I need to change something on the back-end tables,
>>>let say I add some fields. What I used to do is do the changes
>>>here in the office to test and do the same on the customer place
>>>(double job), because if I just copy and overwrite, they will loss
>>>their data.
>>>
>>>What I want is to synchronized only the structure, is there any way
>>>to automate this?
>>>
>>
>>
>>
>>
> 
> 
> 
> 
> 



Message #5 by "Haslett, Andrew" <andrew.haslett@i...> on Wed, 31 Jul 2002 11:22:39 +0930
Maybe I'm missing something, but changing the structure of their back-end
won't change the data.  You don't need to synchronise anything, assuming
you're not using replication.

Simply make the structure changes to the back-end and they will take affect
immediately. Since you've already tested them in your office there should be
no problem.

Cheers,
Andrew


-----Original Message-----
From: George Oro [mailto:george@c...]
Sent: Wednesday, 31 July 2002 12:43 AM
To: Access
Subject: [access] Synchronized only the structure changes


Hi Guys,

What is the best approach to modify the db back-end on site (Customer Place)
automatically without affecting the data?

What I mean is, the db is already installed on my customer place, the setup
is, front-end on each client machine and back-end on the
server. Sometimes I need to change something on the back-end tables, let say
I add some fields. What I used to do is do the changes
here in the office to test and do the same on the customer place (double
job), because if I just copy and overwrite, they will loss
their data.

What I want is to synchronized only the structure, is there any way to
automate this?


Any idea or help is highly appreciated.


Cheers,
George



Message #6 by "George Oro" <george@c...> on Wed, 31 Jul 2002 08:53:17 +0400
Hi Guys,

First thanks for all your time & suggestion...

What you are suggesting now Andrew is what I'm doing at the moment. If is a small changes, it's fine, but if it is a huge one, it's
a pain (double job). Modify in the my office and modify on site.

What I want is just like a Patch file approach, only you have to do is run the file to the clients machine and it will add all your
changes on the back-end without loosing their data.

Hope anyone have a good idea and your still welcome.

Thanks again guys,

George



-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Wednesday, July 31, 2002 5:53 AM
To: Access
Subject: [access] RE: Synchronized only the structure changes


Maybe I'm missing something, but changing the structure of their back-end
won't change the data.  You don't need to synchronise anything, assuming
you're not using replication.

Simply make the structure changes to the back-end and they will take affect
immediately. Since you've already tested them in your office there should be
no problem.

Cheers,
Andrew


-----Original Message-----
From: George Oro [mailto:george@c...]
Sent: Wednesday, 31 July 2002 12:43 AM
To: Access
Subject: [access] Synchronized only the structure changes


Hi Guys,

What is the best approach to modify the db back-end on site (Customer Place)
automatically without affecting the data?

What I mean is, the db is already installed on my customer place, the setup
is, front-end on each client machine and back-end on the
server. Sometimes I need to change something on the back-end tables, let say
I add some fields. What I used to do is do the changes
here in the office to test and do the same on the customer place (double
job), because if I just copy and overwrite, they will loss
their data.

What I want is to synchronized only the structure, is there any way to
automate this?


Any idea or help is highly appreciated.


Cheers,
George





Message #7 by "Wesley Kendrick" <wez.k@n...> on Wed, 31 Jul 2002 12:01:23 +0100
Hi George, what about creating a make-table query which creates an (empty)
table with
the new fields incorporated, then using an append query to write the data
from the old table into the new table. You can then delete the old table and
rename the new table with the old name.
This can all be done in VB, I've done something similar myself
Regards, Wesley Kendrick


----- Original Message -----
From: "George Oro" <george@c...>
To: "Access" <access@p...>
Sent: Wednesday, July 31, 2002 5:53 AM
Subject: [access] RE: Synchronized only the structure changes


> Hi Guys,
>
> First thanks for all your time & suggestion...
>
> What you are suggesting now Andrew is what I'm doing at the moment. If is
a small changes, it's fine, but if it is a huge one, it's
> a pain (double job). Modify in the my office and modify on site.
>
> What I want is just like a Patch file approach, only you have to do is run
the file to the clients machine and it will add all your
> changes on the back-end without loosing their data.
>
> Hope anyone have a good idea and your still welcome.
>
> Thanks again guys,
>
> George
>
>
>
> -----Original Message-----
> From: Haslett, Andrew [mailto:andrew.haslett@i...]
> Sent: Wednesday, July 31, 2002 5:53 AM
> To: Access
> Subject: [access] RE: Synchronized only the structure changes
>
>
> Maybe I'm missing something, but changing the structure of their back-end
> won't change the data.  You don't need to synchronise anything, assuming
> you're not using replication.
>
> Simply make the structure changes to the back-end and they will take
affect
> immediately. Since you've already tested them in your office there should
be
> no problem.
>
> Cheers,
> Andrew
>
>
> -----Original Message-----
> From: George Oro [mailto:george@c...]
> Sent: Wednesday, 31 July 2002 12:43 AM
> To: Access
> Subject: [access] Synchronized only the structure changes
>
>
> Hi Guys,
>
> What is the best approach to modify the db back-end on site (Customer
Place)
> automatically without affecting the data?
>
> What I mean is, the db is already installed on my customer place, the
setup
> is, front-end on each client machine and back-end on the
> server. Sometimes I need to change something on the back-end tables, let
say
> I add some fields. What I used to do is do the changes
> here in the office to test and do the same on the customer place (double
> job), because if I just copy and overwrite, they will loss
> their data.
>
> What I want is to synchronized only the structure, is there any way to
> automate this?
>
>
> Any idea or help is highly appreciated.
>
>
> Cheers,
> George
>
>
>
>
>
>
>

Message #8 by "George Oro" <george@c...> on Wed, 31 Jul 2002 16:58:58 +0400
Hi Wesley,

I guess deleting the original table which is linked to number of tables will cause a problem, correct me if I'm wrong.


Cheers,
George


-----Original Message-----
From: Wesley Kendrick [mailto:wez.k@n...]
Sent: Wednesday, July 31, 2002 3:01 PM
To: Access
Subject: [access] RE: Synchronized only the structure changes


Hi George, what about creating a make-table query which creates an (empty)
table with
the new fields incorporated, then using an append query to write the data
from the old table into the new table. You can then delete the old table and
rename the new table with the old name.
This can all be done in VB, I've done something similar myself
Regards, Wesley Kendrick


----- Original Message -----
From: "George Oro" <george@c...>
To: "Access" <access@p...>
Sent: Wednesday, July 31, 2002 5:53 AM
Subject: [access] RE: Synchronized only the structure changes


> Hi Guys,
>
> First thanks for all your time & suggestion...
>
> What you are suggesting now Andrew is what I'm doing at the moment. If is
a small changes, it's fine, but if it is a huge one, it's
> a pain (double job). Modify in the my office and modify on site.
>
> What I want is just like a Patch file approach, only you have to do is run
the file to the clients machine and it will add all your
> changes on the back-end without loosing their data.
>
> Hope anyone have a good idea and your still welcome.
>
> Thanks again guys,
>
> George
>
>
>
> -----Original Message-----
> From: Haslett, Andrew [mailto:andrew.haslett@i...]
> Sent: Wednesday, July 31, 2002 5:53 AM
> To: Access
> Subject: [access] RE: Synchronized only the structure changes
>
>
> Maybe I'm missing something, but changing the structure of their back-end
> won't change the data.  You don't need to synchronise anything, assuming
> you're not using replication.
>
> Simply make the structure changes to the back-end and they will take
affect
> immediately. Since you've already tested them in your office there should
be
> no problem.
>
> Cheers,
> Andrew
>
>
> -----Original Message-----
> From: George Oro [mailto:george@c...]
> Sent: Wednesday, 31 July 2002 12:43 AM
> To: Access
> Subject: [access] Synchronized only the structure changes
>
>
> Hi Guys,
>
> What is the best approach to modify the db back-end on site (Customer
Place)
> automatically without affecting the data?
>
> What I mean is, the db is already installed on my customer place, the
setup
> is, front-end on each client machine and back-end on the
> server. Sometimes I need to change something on the back-end tables, let
say
> I add some fields. What I used to do is do the changes
> here in the office to test and do the same on the customer place (double
> job), because if I just copy and overwrite, they will loss
> their data.
>
> What I want is to synchronized only the structure, is there any way to
> automate this?
>
>
> Any idea or help is highly appreciated.
>
>
> Cheers,
> George
>
>
>
>
>
>
>




  Return to Index