Creating ODBC Data Source automatically?

[Jozef]

Hello,

Is there any way to automatically create an ODBC data source if it doesn't
already exist?

I'd like to deploy this program on workstations that I may not have access
to, and don't want to rely on the user for any technical expertise. Is
there any way to do that?

Thanks!

[polite person]

How To Create and Remove a DSN in Visual Basic
http://support.microsoft.com/kb/q171146/

[Steve Jorgensen]

On Tue, 30 Aug 2005 14:34:34 GMT, "Jozef" <SP**********@telus.net> wrote:

Hello,

Is there any way to automatically create an ODBC data source if it doesn't
already exist?

I'd like to deploy this program on workstations that I may not have access
to, and don't want to rely on the user for any technical expertise. Is
there any way to do that?

Thanks!

Although you can do that, perhaps, you should use DSNless connections instead.

[Salad]

Steve Jorgensen wrote:

On Tue, 30 Aug 2005 14:34:34 GMT, "Jozef" <SP**********@telus.net> wrote:

Hello,

Is there any way to automatically create an ODBC data source if it doesn't
already exist?

I'd like to deploy this program on workstations that I may not have access
to, and don't want to rely on the user for any technical expertise. Is
there any way to do that?

Thanks!

Although you can do that, perhaps, you should use DSNless connections instead.

Can you describe a DSNless connection, Steve? Is that still ODBC? I
ask because I have a Foxpro DOS table that is SLOW, SLOW, SLOWER than
mollasses if I attempt to link to it via ODBC. In fact, I gave up on
ODBC and FoxPro DOS because it was so terrible. I would have thought
since FoxPro was a MS product, MS could make some of their products work
together....especially a simple database like FoxPro.

[pietlinden]

Salad,
Carl Prothman has examples of just about every connection string
(DSN-less too) that you can think of. And if one's missing, you could
probably e-mail him...
www.able-consulting.com
there's a whole section on connection strings. a BIG one.

[Steve Jorgensen]

On Tue, 30 Aug 2005 16:28:04 GMT, Salad <oi*@vinegar.com> wrote:

Steve Jorgensen wrote:

On Tue, 30 Aug 2005 14:34:34 GMT, "Jozef" <SP**********@telus.net> wrote:

Hello,

Is there any way to automatically create an ODBC data source if it doesn't
already exist?

I'd like to deploy this program on workstations that I may not have access
to, and don't want to rely on the user for any technical expertise. Is
there any way to do that?

Thanks!

Although you can do that, perhaps, you should use DSNless connections instead.

Can you describe a DSNless connection, Steve? Is that still ODBC? I
ask because I have a Foxpro DOS table that is SLOW, SLOW, SLOWER than
mollasses if I attempt to link to it via ODBC. In fact, I gave up on
ODBC and FoxPro DOS because it was so terrible. I would have thought
since FoxPro was a MS product, MS could make some of their products work
together....especially a simple database like FoxPro.

All a DSNless connectino means is that you use a conneciton string that
includes all teh options explicitly in the string rather than storing them in
a DSN, and referencing the DSN. You're still using the same libraries and
layers, so unfortunately this will not help with your performance issue at
all.

[Salad]

Steve Jorgensen wrote:

On Tue, 30 Aug 2005 16:28:04 GMT, Salad <oi*@vinegar.com> wrote:

Steve Jorgensen wrote:

On Tue, 30 Aug 2005 14:34:34 GMT, "Jozef" <SP**********@telus.net> wrote:

Hello,

Is there any way to automatically create an ODBC data source if it doesn't
already exist?

I'd like to deploy this program on workstations that I may not have access
to, and don't want to rely on the user for any technical expertise. Is
there any way to do that?

Thanks!

Although you can do that, perhaps, you should use DSNless connections instead.

Can you describe a DSNless connection, Steve? Is that still ODBC? I
ask because I have a Foxpro DOS table that is SLOW, SLOW, SLOWER than
mollasses if I attempt to link to it via ODBC. In fact, I gave up on
ODBC and FoxPro DOS because it was so terrible. I would have thought
since FoxPro was a MS product, MS could make some of their products work
together....especially a simple database like FoxPro.

All a DSNless connectino means is that you use a conneciton string that
includes all teh options explicitly in the string rather than storing them in
a DSN, and referencing the DSN. You're still using the same libraries and
layers, so unfortunately this will not help with your performance issue at
all.

Gotcha.