C
Chester West
OK...I give up
It would seem like Microsoft decided that they really
liked SQL server, and so made it impossible for .NET to
talk to ACCESS.
I am using the 1.0 framework.
I was getting a "The Microsoft Jet database engine cannot
open the file <filename>. It is already opened exclusively
by another user, or you need permission to view its data."
message.
This led me to KB 316675.
So...I modified the machine.conf file (which means that,
although I MIGHT get it to work on my machine, it probably
won't work when it is hosted on the ISP) and behold...Now
I get the message "Cannot Lock File" when I try to open
the file to perform a SQL select statement.
Pardon my french, but WHAT THE HELL DO I NEED TO DO TO GET
THIS STUPID THING WORKING?
Can somebody provide a code sample????
Thanks
It would seem like Microsoft decided that they really
liked SQL server, and so made it impossible for .NET to
talk to ACCESS.
I am using the 1.0 framework.
I was getting a "The Microsoft Jet database engine cannot
open the file <filename>. It is already opened exclusively
by another user, or you need permission to view its data."
message.
This led me to KB 316675.
So...I modified the machine.conf file (which means that,
although I MIGHT get it to work on my machine, it probably
won't work when it is hosted on the ISP) and behold...Now
I get the message "Cannot Lock File" when I try to open
the file to perform a SQL select statement.
Pardon my french, but WHAT THE HELL DO I NEED TO DO TO GET
THIS STUPID THING WORKING?
Can somebody provide a code sample????
Thanks