Typically, you write some scripts, which use "CREATE
[TABLE|VIEW\PROCEDURE]..." or "ALTER [TABLE|VIEW|PROCEDURE" to modify the BE
Sql Server in use. Then you use tool, such as isql.exe or Query Analyzer to
execute these sql script. You can also write your own DB update tool in ADO,
ADO.NET, DMO... to do the upating, so that the updating would be more
transparent to your client, espcially if your clients do not have a
qualified DB administrator.
> Hello,
>
[quoted text clipped - 23 lines]
>
> Thanks in advance for your help
Norman Yuan - 20 Feb 2006 14:14 GMT
Sorry, by "isql.exe", I really meant "osql.exe".
> Typically, you write some scripts, which use "CREATE
> [TABLE|VIEW\PROCEDURE]..." or "ALTER [TABLE|VIEW|PROCEDURE" to modify the
[quoted text clipped - 31 lines]
>>
>> Thanks in advance for your help
David - 20 Feb 2006 15:45 GMT
Unfortunatelly, I am using only Access to create views or procedures which
hides the CREATE/ALTER format of an SQL query. Using the Access you see just
SELECT, INSERT etc. so it does not make the job easy.
The way you recommend seems to be pretty complicated - using some kind of ADO
code (Can it be written in Access?) I should extract the SQL queries from my
local SQL Server version and then run it by customer if I want to make it
compatible with a new FE release.
Is there really nothing easier? Do I need to write everything by myself?
Personally, I use the Red-Gate SQL-Compare tool for this purpose. Great
product; had paid for itself after the first use: http://www.red-gate.com/

Signature
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
> Hello,
>
[quoted text clipped - 23 lines]
>
> Thanks in advance for your help