Okay... the subject line doesn't allow enough text for the actual problem.
As mentioned, I'm using an ADODB.Connection to return an ADODB.Recordset object based upon running a SELECT statement against a CSV file. So far so good, right? This much works fine...
...the problem happens if I have to different workstations essentially accessing the same CSV file. The first one to hit the CSV has no problem. The second one to hit, if the first one still is reading records from the recordset, gets the following error:
[ QUOTE ]
Microsoft OLE DB Provider for ODBC Drivers [Microsoft][ODBC Text Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
[/ QUOTE ]
The CSV file is stored on a server drive and the user logged into the workstation has full read/write access to the files on that drive location. I don't have any explicit ODBC driver settings setup in the control panel.
Is there anything I can set on the Connection object, either on the object itself or in the connection string, that will allow two workstations to hit the same file at the same time?
Another configuration I've tried is that, instead of calling ADODB.Connection.Execute to return the record set, I've called ADODB.RecordSet.Open, passing in the conneciton, and setting the recordset mode to a optimistic lock.
Anyone got any ideas?
Automated Testing Evangelists
Definition expert - noun - Unknown drip under pressure