Steve,
You write "What if the destination server will not have Access or SQL
applications" in your message. Concider that when you write software
you target is for a given platform. This platform does not only define
which operating system (and version) to use, but also things like what
..NET Framework version to target as well as what data store to use.
This said, you write application which depend on a given data store
(unless you use strict ANSI compliant SQL statements, but that is
rarly the case since you loose things such as performance and
functionality). Of course you could provide your application with
the ability to use different data adapters, depending on configuration
settings.
So lets say you develoop an application which is aimed at SQL
Server. Depending on the features your application requires, you
application may be able to use MSDE as a cheep and small
option.
One way would be to ship an *.sql file with your installer which
executes all of the DDL (Data Definition Language, like CREATE
TABLE etc.) when the application is installed (SQL Server and
MSDN ships with command line applications to do things like
this) or you could have your application detect a "first-run" and
execute the *.sql file then, using ADO.NET.
If you don't have VS.NET, then there are many commercial
application which can be used to create install packages. I bet
there are a few free once as well out there. Remember that
even though a commercial tool might set you back a few $, you
should factor in the cost in the price of the software (for instance
you might calculate that selling 1000 copies will pay for the
installer tool).
Hope this helps,
//Andreas
