Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Connection string
Mon, Mar 22 2010 5:38 AMPermanent Link

Tiago Ameller

Menorca Zeros i Uns SL

Avatar

I'm trying to connect from a 3rt party application to our DBISAM 4 files using ODBC, I've installed DBISAM4 ODBC demo and configured a DSN file. This 3rt party application doesn't provide any information to how create the connection string, just a single button to test it. I put this

FILEDSN="c:\path\myfile.DSN"

The error is "An OLE DB provider was not specified in the connection string. An example would be "PROVIDER=OLEDB"

This application runs over .NET 2

Any suggestion?

myfile.DSN file is here:

[ODBC]
DRIVER=DBISAM 4 ODBC Driver (Read-Only)
UID=
PrivateDirectory=C:\DOCUME~1\Usuario\CONFIG~1\Temp\
MRUPrivateDirectory1=C:\DOCUME~1\Usuario\CONFIG~1\Temp\
StrictChangeDetection=False
ForceBufferFlush=False
LockWaitTime=100
LockRetryCount=15
ReadOnly=True
CatalogName=C:\SSC\SisFactu\DATA\EM000001
MRUDatabase2=C:\SSC\SisFactu\DATA\EM000001
MRUDatabase1=Memory
RemoteReadAhead=50
RemoteEncryptionPassword=elevatesoft
RemoteEncryption=False
RemotePingInterval=60
RemotePing=False
RemoteCompression=0
RemoteService=
RemotePort=12005
RemoteIPAddress=127.0.0.1
RemoteHostName=
ConnectionType=Local
Mon, Mar 22 2010 9:39 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi Santiago,

I have not tried using a FILESDN but when I make my connection string I
have to wrap the driver with {} like this:

DRIVER={DBISAM 4 ODBC Driver}

might be worth trying.

Chris Holland
[Team Elevate]


On 22/03/2010 09:38, Santiago Ameller wrote:
> I'm trying to connect from a 3rt party application to our DBISAM 4 files using ODBC, I've installed DBISAM4 ODBC demo and configured a DSN file. This 3rt party application doesn't provide any information to how create the connection string, just a single button to test it. I put this
>
> FILEDSN="c:\path\myfile.DSN"
>
> The error is "An OLE DB provider was not specified in the connection string. An example would be "PROVIDER=OLEDB"
>
> This application runs over .NET 2
>
> Any suggestion?
>
> myfile.DSN file is here:
>
> [ODBC]
> DRIVER=DBISAM 4 ODBC Driver (Read-Only)
> UID=
> PrivateDirectory=C:\DOCUME~1\Usuario\CONFIG~1\Temp\
> MRUPrivateDirectory1=C:\DOCUME~1\Usuario\CONFIG~1\Temp\
> StrictChangeDetection=False
> ForceBufferFlush=False
> LockWaitTime=100
> LockRetryCount=15
> ReadOnly=True
> CatalogName=C:\SSC\SisFactu\DATA\EM000001
> MRUDatabase2=C:\SSC\SisFactu\DATA\EM000001
> MRUDatabase1=Memory
> RemoteReadAhead=50
> RemoteEncryptionPassword=elevatesoft
> RemoteEncryption=False
> RemotePingInterval=60
> RemotePing=False
> RemoteCompression=0
> RemoteService=
> RemotePort=12005
> RemoteIPAddress=127.0.0.1
> RemoteHostName=
> ConnectionType=Local
>

--
Mon, Mar 22 2010 12:08 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Santiago,

<< I'm trying to connect from a 3rt party application to our DBISAM 4 files
using ODBC, I've installed DBISAM4 ODBC demo and configured a DSN file. This
3rt party application doesn't provide any information to how create the
connection string, just a single button to test it. I put this

FILEDSN="c:\path\myfile.DSN"

The error is "An OLE DB provider was not specified in the connection
string. An example would be PROVIDER=OLEDB" >>

What you need is an OLEDB provider connection string - you can create one
using the ADO components in Delphi.  For example, here's one created using
the TADOConnection component's property editor for the ConnectionString
property:

Provider=MSDASQL.1;Persist Security Info=False;Data Source=Test

where the Data Source attribute is the name of the DSN.

You can't use a file-based DSN with the OLEDB provider for ODBC data
sources.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Mar 22 2010 12:55 PMPermanent Link

Tiago Ameller

Menorca Zeros i Uns SL

Avatar

Thanks, Chris. I did that before posting here, with no success.

Tim,

With your connection string, now it is raising:

"The .net Framework Data Provider for OLEDB (System.Data.OleDb) does no support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider of ODBC (System.Data.Odbc)."

I'm testing this on vmware machine XP SP2 with almost nothing installed, just DBISAM4 files and .net 2 in order to reproduce in the minimal scenario to deploy (if it runs I'll buy DBISAM4 ODBC, of course Wink

I think there is missing some piece of software. I'll also ask the app vendor some help.
Tue, Mar 23 2010 5:14 AMPermanent Link

Tiago Ameller

Menorca Zeros i Uns SL

Avatar

Tim,

Talking with the app support, who already had a customer using DBISAM4 ODBC. She gave me the right connection string: "ODBC;DSN=SF000001", where SF000001 is the DSN name.

Issue fixed! Smile
Tue, Mar 23 2010 11:49 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tiago,

<< Talking with the app support, who already had a customer using DBISAM4
ODBC. She gave me the right connection string: "ODBC;DSN=SF000001", where
SF000001 is the DSN name.

Issue fixed! Smile>>

Great, thanks for the update.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image