remote ODBC data source

**nashman** · 10th December 2007, 01:23

Originally Posted by mchara

I think the reason is different, because firewalls are turned off on both machines and they are in local network so there's no firewalls between...
I rather suppose some stopped services are required, but i don't want to turn on everything without knowledge what those services do.

Or qt ignores hostName in odbc driver... it can be part of common interface for dBase drivers, but ignored by ODBC driver's implementation.

Is dBase the type of database you are attempting to connect to? Which/whose ODBC driver are you using?

**mchara** · 10th December 2007, 07:10

I've tried for access, excel and msSql, everything works fine for datasources defined locally, but ODBC driver reports error when trying to use datasource defined at remote machine. We have to PCs with identical databases defined and tried to connect to them in both directions.

Windows firewall is also turned of in every machine because we are using VNC software in company and it can't work with firewall.

**mm78** · 10th December 2007, 10:34

What do you mean with "datasource defined at remote machine"?

The ODBC driver ignores host name and port and relies only on the datasources defined on the host machine. The datasource can point to a remote database of course.

You may be able to work around this by passing an ODBC connection string as database name, e.g.:
DRIVER={SQL Native Client};SERVER=SERVERNAME\INSTANCENAME;

**mchara** · 10th December 2007, 10:39

So, it's simply impossible to connect to data source not defined on host...

As i tough at the beginning
qt ignores hostName in odbc driver - it's part of common interface for dBase drivers used by other drivers.

I'm quite sure now, thanks!