ODBC connect failed

[afrosteve]

Hi

I am investigating adapting an existing tool that extracts input data from various systems to then put into a legacy system.

Currently that data can come from a variety of sources, either via XML/SOAP or from a db via ODBC.

To do this for filemaker, the XML option has been ruled out by the client due to security considerations so we are following the ODBC route.

This all worked fine in a test environment when the machine had our interface table (myfile.fp5) open

BUT if filemaker is not currently running using the connection object to open a recordset (we are in VB here) returns:

[filemaker][ODBC filemaker driver][filemaker pro]connect failed

if filemaker is open (say with test.fp5) BUT our file is NOT OPEN we get:

[filemaker][ODBC filemaker driver][filemaker pro]database not open

Given that we CANNOT use the web companion is a requirement of the filemaker ODBC driver that the database file to be accessed is up and running??

The client had indicated that they do not want a file left permanently open as they were already nearing limits on their server box as to # of open files.

Can someone out there in the filemaker community let me know what the score is here.

Thanks

Steve

[slstrother]

Unfortunately, the file must be up and running.