BorlandTalk.com

Jignesh Doshi · Guest

We have Database Application built with Delphi 6 using BDE/ODBC and SQL
Server 2000 database.

I have a few questions that I need to ask here.

- Server Side Installation:

There will be two scenarios here:

1 The Clients who does not have SQL Server installed.
I am not sure if anyone is familiar with licensing method called 'Runtime
SQL Server License' I will be using that method of Licensing to provide this
SQL Server to my low end clients I am looking for some more information on
How to implement this type of SQL Server installation? After SQL Server
installed then I will need to resolve the same issue as in the 2nd scenario

2 The Clients who already has SQL Server installed.
I will need to include 3 databases on which I use SQL Server authentication,
to be included and attached as a part of Server side installation. All
databases will not be blank (will have some data), so I won't be able to
script those database to be generated as a part of installation What is the
best suggestion to ship and attach databases as a part of server side
installation.

- Client Side Installation:
1 BDE Installation:
I will be using Installshield Express that came with Delphi to install BDE.

2 ODBC DSN:
I can use Installshield to create DSNs but It does not allow to have User
enter SQL Server name and Database Name What is the best way for
User installing client CD have select the SQL Server and Database Name at
the time of installation? Also I will need to make some changes on BDE like
'Blob Size' and 'Blob to Cache' at the time of installation How can I do
that?

Thank for any response in Advance.

Oscar Santiesteban Jr. · Guest

"Clients who does not have SQL SERVER installed"
They have to buy SQL server either a processor license or per seat
licensing. Maybe with SQL 2005 Express (the current MSDE) you will be able
to do something, but I suggest you have the client purchase SQL Standard
Edition. I have never heard of this "Runtime Licensing".

"Client that has SQL server"
The best idea I have seen so far, since you are sending a database that is
not blank, is that you "detach" the database from you SQL Server and the
client "attaches" the database on their side. This can be scripted but you
have to know the path of the directories on the clients side.

As an overall suggestion, unless you have a reason for using BDE, I would go
with ADO instead. That way you can skip the BDE installation and the ODBC
installation.

Oscar...

"Jignesh Doshi" <nospam (AT) nospam (DOT) com> wrote