MS SQL Server 2005 - Client Files

[NewsArchive]

Can anyone point me in the direction of how to have SetupBuilder install the
required on a computer that's needed if my C6 app uses MSSQL Server 2005 ?

Thanks,
Don G.
Krontz Media

[NewsArchive]

Sorry - looks like I left out a little bit of text.

I meant to ask for help installing the required files that my C6 app using
MSSQL Server 2005 needs to run.

Thanks,
Don G.
Krontz Media

[NewsArchive]

Don,

> Sorry - looks like I left out a little bit of text.
>
> I meant to ask for help installing the required files that my C6 app using
> MSSQL Server 2005 needs to run.

You only have to install the "SQL Server" driver (see "Install ODBC
Driver...") and to Configure a ODBC Data Source (see "Config ODBC Data
Source") and you should be done.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

>
> You only have to install the "SQL Server" driver (see "Install ODBC
> Driver...") and to Configure a ODBC Data Source (see "Config ODBC Data
> Source") and you should be done.
>
Are we talking about SB here? I plan on spending the day reading up on this
as well as David and Arnors documents on the UAC stuff.

Thanks Friedrich.
Don
Krontz Media

[NewsArchive]

Hi Don,

>> You only have to install the "SQL Server" driver (see "Install ODBC
>> Driver...") and to Configure a ODBC Data Source (see "Config ODBC Data
>> Source") and you should be done.
>>
> Are we talking about SB here? I plan on spending the day reading up on
> this as well as David and Arnors documents on the UAC stuff.

Yes, sorry for the confusion. I am talking about the built-in SetupBuilder
script functions.

Friedrich

[NewsArchive]

No - Friedrich - please - no apology - you've been a great help to me and
many others.

Have a great day.

Don
Krontz Media

[NewsArchive]

Hi Friedrich,
>
> You only have to install the "SQL Server" driver (see "Install ODBC
> Driver...") and to Configure a ODBC Data Source (see "Config ODBC Data
> Source") and you should be done.
>
Do you have an example script for doing this that I can download somewhere?

PS: My personal email is xxxxxx.xxxxxx@xxxxl.com

Thanks,
Don

[NewsArchive]

Hi Don,

> Do you have an example script for doing this that I can download
> somewhere?
>
> PS: My personal email is xxxxxx.xxxxxx@xxxxx.xxx

Unfortunately, no. There are too many ODBC drivers out there. The required
parameters are different for each and every ODBC provider. The ODBC manual
(in this case for SQL Server) should provide all the information to install
an ODBC driver and (system) DSN.

If you have the SQL ODBC driver on your machine, you can import it (see
attached screenshots).

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

I've got the ODBC driver importing just fine - but need to configure it.
When I look in your help under "Configure ODBC Data Source" - points me to
"Call DLL" - which shows absolutely nothing about configuring an ODBC Data
Source.

Man - I'm stuck here with my boss breathing down my neck, and cannot give
him an answer.

Don
Krontz Media

[NewsArchive]

Hi Don,

> I've got the ODBC driver importing just fine - but need to configure it.
> When I look in your help under "Configure ODBC Data Source" - points me
> to "Call DLL" - which shows absolutely nothing about configuring an ODBC
> Data Source.

I just checked this and it's fine in SB7 (see attached screenshot).

Friedrich

[NewsArchive]

>
> I just checked this and it's fine in SB7 (see attached screenshot).
>
Yes - I'm sure it does. But that doesn't help with the version we bought a
year ago and have never used, and now I've got a boss mad as hell at me for
not being able to deliver an installable to some of our clients. If my
budget permitted it - I'd buy the new SB7 license myself - but at this
point - cannot do it.

So, looks like the end result is - is that I'm stuck with not being able to
package our product with SB6.xx that we have.

??

Don
Krontz Media

[NewsArchive]

> Yes - I'm sure it does. But that doesn't help with the version we bought
> a
> year ago and have never used, and now I've got a boss mad as hell at me
> for not being able to deliver an installable to some of our clients. If
> my budget permitted it - I'd buy the new SB7 license myself - but at this
> point - cannot do it.
>
> So, looks like the end result is - is that I'm stuck with not being able
> to package our product with SB6.xx that we have.
>
> ??

I have no idea what you are talking about. Why can't you do it with SB6?
What does the documentation has to do with that? Just download the latest
documentation (free-of-charge) and you are done.

And BTW, you don't need a new license to go to SB7. You only need an active
subscription to update to the latest version. Your SetupBuilder license
will never expire.

Friedrich

[NewsArchive]

Hi Friedrich,
Turns out that I don't need the ODBC driver at all. It's the "SQL Server
Native Client" that's needed. No data source to configure or nothing -
which makes sense because the data source is pretty much configured in the
connection string.

I've installed it - it's an .MSI, and that fixed it - so now all I've got to
do is figure out how to make it install silently. The only parameters are
The Name and Organization - simple stuff. I'm checking to see if it
supports command line silent install or not.

Thanks for your help though,
Don
Krontz Media

[NewsArchive]

Friedrich, another question: Can you give me an idea on how to bypass the
"Open File - Security Warning" dialog. If I can get around this - I've got
it beat! The sqlncli.msi does support command-line arguments - you can type
this from the command prompt: sqlncli.msi /passive or use the /quite switch
and it will install w/o user interaction. Just need to get around the open
file warning dialog.

For others that are needing to install the SQL Server Client stuff - Might
want to take a look at this thread. Looks like the SQL Server Native Client
takes care of the connection as long as you have a valid Connection String.

Thanks,
Don

[NewsArchive]

Hi one more time Friedrich <g>.

I GOT IT <G> !!!

Ended up using the "Run Windows Installer" and put it at the end of the
script to run the sqlncli.msi with the /quiet switch - works like a frickin
champ!

Pretty slick - don't need no ODBC Driver to be installed, no Data Source to
configure - just simply install the native client and let the connection
string do the rest.

Anyway, thanks for opening my eyes and forcing me to read more into what I
was attempting to do.

Thanks,
Don
Krontz Media

[NewsArchive]

> Man - I'm stuck here with my boss breathing down my neck, and cannot give
> him an answer.

BTW, the Webinar is online right now...

Friedrich

[NewsArchive]

> I GOT IT <G> !!!
>
> Ended up using the "Run Windows Installer" and put it at the end of the
> script to run the sqlncli.msi with the /quiet switch - works like a
> frickin champ!

COOL!

Thanks for the update.

Friedrich