ACCESS accessibility from a C++ process launched from an ACCESS form

[Fred F.]

Here is my problem. From an ACCESS form, I run a C++ process reaching
the same database in read/write mode via the ODBC driver. An error
occurs: " The database has been placed by an unknown user in a state
preventing it from being opened either locked. SQLSetConnectAt tr
failure of the pilot " (Nota : translated approximatively from the
french error message). However, if I have used an another form before
(eg. to modify a table), or if I have modified myself a record of any
table, there is no problem. It seems that the database is in a state "
read-only " by default until there is some modification made directly
with ACCESS.
Do you know a mean to solve this problem or to make this manual
operation automatically/systematically ? Thanks.

System used : Windows XP pro
Access used : ACCESS 2002

[Tom C]

Sorry Fred, I'm not familiar with your problem. From what you wrote however,
this is
what I would do (until I found a better solution):

1. Create a Temp Table with one field (of any type, I would use yes/no)
let's call it tblTempODBC_Unl ock

2. On the "On Open" event of the form that runs the C++ process add code
to open the table, change the value of the first field, save the changes
and
close the table.

now you should be ready to use your C++ process without any problems!

Good Luck

Tom C
"Fred F." <ff********@ifr ance.com> wrote in message
news:90******** *************** **@posting.goog le.com...

Here is my problem. From an ACCESS form, I run a C++ process reaching
the same database in read/write mode via the ODBC driver. An error
occurs: " The database has been placed by an unknown user in a state
preventing it from being opened either locked. SQLSetConnectAt tr
failure of the pilot " (Nota : translated approximatively from the
french error message). However, if I have used an another form before
(eg. to modify a table), or if I have modified myself a record of any
table, there is no problem. It seems that the database is in a state "
read-only " by default until there is some modification made directly
with ACCESS.
Do you know a mean to solve this problem or to make this manual
operation automatically/systematically ? Thanks.

System used : Windows XP pro
Access used : ACCESS 2002