Hi,

I'm developping a side application for a client that use Paradox 5.x
tables
as a DataBase.

My application is in .NET 2.0, using OleDb to connect to the database.

On a Windows XP OS, I can run my application at the same time as I run
their.

But on Windows Vista Business 32-bit (Probably other Vista, but that's
the
only one I tried yet) I cannot run my application while their
application
is running.

I get the error "The microsoft Jet database engin could not find the
object
'mytable'. Make sure the object exists and that you spell its name and
the
path name correctly."

Ok, I'm sure the file exist and its spelled correctly. It only happen
when
I run their application. Like a cocurrent read/write on the database.

My side application only need to READ, so I tried setting the OleDb
driver
mode to read but it didn't fix the problem.

If anyone can help me, please do so as I tried everything and don't
know
what to do now.

If you need more informations, please tell me and I'll give it.


Thank you

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Both systems need to configure to use a
** shared netdir ** in the ---> BDE.

Unless you use the same netdir, the BDE will prevent the second one into
the table (directory) from accessing it.

NOTE: The paths used to the netdir must be EXACTLY THE SAME in both
instances of the BDE.

NOT resolved to, but EXACTLY THE SAME, CHARACTER FOR CHARACTER. You CAN
get away with a different drive letter, but that is the only difference
allowed.


Tony McGuire



deathwearer (AT) gmail (DOT) com wrote:

Thank Tony,

I'll take a look at it.

But the customer application is in Delphi and using the BDE to connect
to the DataBase.

On the other hand my application is written in C# 2.0 and using OleDb
JET.4 to connect to the database. Sure the BDE still need to be
installed, but is it using the same netdir as the delphi application?
Or is there something I need to set somewhere? Cause you say make sure
they both use the same netdir, but I can only configure the netdir in
the BDE Administration and not at two place. So I'm a bit lost.


Thank for your help.

Thank Tony,

I'll take a look at it.

But the customer application is in Delphi and using the BDE to connect
to the DataBase.

On the other hand my application is written in C# 2.0 and using OleDb
JET.4 to connect to the database. Sure the BDE still need to be
installed, but is it using the same netdir as the delphi application?
Or is there something I need to set somewhere? Cause you say make sure
they both use the same netdir, but I can only configure the netdir in
the BDE Administration and not at two place. So I'm a bit lost.


Thank for your help.