If I understand correctly, why not just generate change scripts for whatever is different on the server and put them in a folder. When the laptops come in and hookup, the go to that folder and run the change scripts. Give each script a guid as a name and let the laptops maintain a list of guids for scripts they have run, only running those that haven't been run before. Probably need to figure out sequencing but that shouldn't be too difficult, especially if you assign the guids as newsequentialguids ( or just some other id system )

Redgate tools could probably make the script generation pretty easy.

>This C#/SQL Server Express application runs on laptops that are out on delivery trucks all day and return to the office in the evening.
>The laptops have no internet access for a variety of business reasons.
>
>A synchronization program that runs on the laptop places XML information extracted from the laptop tables in a folder on the server in the office. That operation uses an ethernet cat 5 connection.
>Another C# program on the laptop looks in another folder on the server for updates to the processing program and installs them on the laptop.
>For security reasons, the laptop has no access to the SQL Server at the office- just certain folders on the server.
>Later, the server runs a program that uses the XML data left by the laptops to update SQL Server tables.
>
>
>That sounds primitive, but it's working pretty well.
>
>However I can't come up with a good way to bring over changes to SQL table structures, stored procedures, views, indexes, etc on the laptop seamlessly.
>
>Any ideas?