----- Original Message -----
From: "Richard Wesley" <hawkfish@...>
> > So, why do you want to add a unneeded restriction to the user?
>
> If you are writing a connection dialog, the UI will look quite
> different to the user for these two options. The embedded version
> will only have a choose file control (for the database) and maybe a
> user name for table access authorisation. The server version will
> also have a server name, a uid/password pair (which must be
> validated) and a database name edit box (without a choose file
> option). Depending on your application, users might find such a
> dialog hard to navigate...

Whenever I write an app that uses the embedded server, under program options
I supply the user with a checkbox. They select whether they are using
standalone (embedded) mode or network mode. I then display what is needed
for either mode based on their choice. All information is stored in the
program .dat file so the program can read it when starting and know which
way to go. Maybe something like that could help you with your design.

HTH

Woody (TMW)