|
 |
asp_databases thread: Oh no not again Error 80004005
Message #1 by sgarstin@t... on Thu, 16 Nov 2000 19:04:44 -0000
|
|
When trying to add records to a database via an APPEND query using ASP I
keep getting the following message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access Driver] Could not update; currently
locked by user 'admin' on machine 'DEFAULT'.
/nss/asp/clienttojob_proc_new_recs.asp, line 293
The message occurs even when Access 2000 itself is closed. I am running
stuff locally under PWS (Win 98) so no one else is accessing the database.
The only clues are:
a. This only happens when there is a one-to-many relationship join between
tables,
and
b. The only way to solve this appears to be to copy each table, query,
form etc.. into a new database WITH A DIFFERENT NAME.
This is deeply worrying and it would be much better to solve the problem
than avoid it (how can I be sure this will not occur when the database is
copied on-line ?).
Can anyone help ?
regds
Simon G
Message #2 by "Ken Schaefer" <ken@a...> on Fri, 17 Nov 2000 11:21:09 +1100
|
|
Are you opening recordsets with adLockPessimistic?
Are you using InterDev?
Cheers
Ken
----- Original Message -----
From: <sgarstin@t...>
To: "ASP Databases" <asp_databases@p...>
Sent: Friday, November 17, 2000 6:04 AM
Subject: [asp_databases] Oh no not again Error 80004005
> When trying to add records to a database via an APPEND query using ASP I
> keep getting the following message:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>
> [Microsoft][ODBC Microsoft Access Driver] Could not update; currently
> locked by user 'admin' on machine 'DEFAULT'.
>
> /nss/asp/clienttojob_proc_new_recs.asp, line 293
>
>
> The message occurs even when Access 2000 itself is closed. I am running
> stuff locally under PWS (Win 98) so no one else is accessing the database.
> The only clues are:
>
> a. This only happens when there is a one-to-many relationship join between
> tables,
> and
> b. The only way to solve this appears to be to copy each table, query,
> form etc.. into a new database WITH A DIFFERENT NAME.
>
> This is deeply worrying and it would be much better to solve the problem
> than avoid it (how can I be sure this will not occur when the database is
> copied on-line ?).
>
> Can anyone help ?
>
> regds
>
>
> Simon G
>
Message #3 by "peter" <ph@t...> on Thu, 16 Nov 2000 23:25:24 -0000
|
|
There is still a database connection present in edit mode. Try a reboot
then run it once, if that works then check it the second time, if it hangs
check the code to see whats keeping the connection open.
HTH
peter
Message #4 by Simon Garstin <Sgarstin@t...> on Fri, 17 Nov 2000 12:17:52 +0000
|
|
Since an APPEND query is being used, I'm using the parameters collection
under ADODB.Command, so the lock parameters are not being called.
No, I'm not using InterDev.
What is actually happening:
I'm attempting to append 16 records - SOME OF THE RECORDS ARE BEING
SUCCESSFULLY APPENDED before it comes up with the error message, but the
actual number of successful records varies each time (between 5 and 12!).
This may be a clue - there are 2 tables being written to: and when the JOIN
relationship between the 2 tables is deleted the operation is ALWAYS
carried out successfully - which tends to eliminate the "database is still
being edited by something else" theory.
Any further ideas ?
regds
Simon G
At 11:21 17/11/00 +1100, you wrote:
>Are you opening recordsets with adLockPessimistic?
>
>Are you using InterDev?
>
>Cheers
>Ken
>
>----- Original Message -----
>From: <sgarstin@t...>
>To: "ASP Databases" <asp_databases@p...>
>Sent: Friday, November 17, 2000 6:04 AM
>Subject: [asp_databases] Oh no not again Error 80004005
>
>
> > When trying to add records to a database via an APPEND query using ASP I
> > keep getting the following message:
> >
> > Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> >
> > [Microsoft][ODBC Microsoft Access Driver] Could not update; currently
> > locked by user 'admin' on machine 'DEFAULT'.
> >
> > /nss/asp/clienttojob_proc_new_recs.asp, line 293
> >
> >
> > The message occurs even when Access 2000 itself is closed. I am running
> > stuff locally under PWS (Win 98) so no one else is accessing the database.
> > The only clues are:
> >
> > a. This only happens when there is a one-to-many relationship join between
> > tables,
> > and
> > b. The only way to solve this appears to be to copy each table, query,
> > form etc.. into a new database WITH A DIFFERENT NAME.
> >
> > This is deeply worrying and it would be much better to solve the problem
> > than avoid it (how can I be sure this will not occur when the database is
> > copied on-line ?).
> >
> > Can anyone help ?
> >
> > regds
> >
> >
> > Simon G
> >
>
>
>
|
|
|
View Cart
