What exactly does the above (subject) error mean? I'm getting it from an
adp file when used by a few people at the same time (each user has the
file in their own filespace though). Access is through windows
authentication and it only seemed to occur during an update of a
specific table.. The problem is it didn't happen to everyone and I
can't recreate it at all on my own, so am wondering if it was something
to do with the level of traffic to/from the server at that specific time.
Any clues?
Cheers,
Chris"Not Me" <not.me@.nowherefake.addr3s.com> wrote in message
news:ccb0fn$n2l$1@.ucsnew1.ncl.ac.uk...
> Hi,
> What exactly does the above (subject) error mean? I'm getting it from an
> adp file when used by a few people at the same time (each user has the
> file in their own filespace though). Access is through windows
> authentication and it only seemed to occur during an update of a
> specific table.. The problem is it didn't happen to everyone and I
> can't recreate it at all on my own, so am wondering if it was something
> to do with the level of traffic to/from the server at that specific time.
Further to this, we seem to be getting strange occurences of the subform
jumping between records. For example we're on one record, we tick a checkbox
then suddenly we're on a different record and it's that records' checkbox
that's been edited! This is all on the same table in the same subform...
Please help!!
Chris|||Not Me (clhumphreys@.toofgib.moc) writes:
> "Not Me" <not.me@.nowherefake.addr3s.com> wrote in message
> news:ccb0fn$n2l$1@.ucsnew1.ncl.ac.uk...
>> What exactly does the above (subject) error mean? I'm getting it from an
>> adp file when used by a few people at the same time (each user has the
>> file in their own filespace though). Access is through windows
>> authentication and it only seemed to occur during an update of a
>> specific table.. The problem is it didn't happen to everyone and I
>> can't recreate it at all on my own, so am wondering if it was something
>> to do with the level of traffic to/from the server at that specific time.
> Further to this, we seem to be getting strange occurences of the subform
> jumping between records. For example we're on one record, we tick a
> checkbox then suddenly we're on a different record and it's that
> records' checkbox that's been edited! This is all on the same table in
> the same subform...
Is that the exact error message? Or does it come with some mumbo-jumbo
around it? In such case, please post the mumbo-jumbo.
However, I don't really think this is an SQL Server problem, but more
likely to be some accident that happens in Access, so you might better
off asking in comp.databases.ms-access.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> Not Me (clhumphreys@.toofgib.moc) writes:
>>"Not Me" <not.me@.nowherefake.addr3s.com> wrote in message
>>news:ccb0fn$n2l$1@.ucsnew1.ncl.ac.uk...
>>
>>>What exactly does the above (subject) error mean? I'm getting it from an
>>>adp file when used by a few people at the same time (each user has the
>>>file in their own filespace though). Access is through windows
>>>authentication and it only seemed to occur during an update of a
>>>specific table.. The problem is it didn't happen to everyone and I
>>>can't recreate it at all on my own, so am wondering if it was something
>>>to do with the level of traffic to/from the server at that specific time.
>>
>>Further to this, we seem to be getting strange occurences of the subform
>>jumping between records. For example we're on one record, we tick a
>>checkbox then suddenly we're on a different record and it's that
>>records' checkbox that's been edited! This is all on the same table in
>>the same subform...
>
> Is that the exact error message? Or does it come with some mumbo-jumbo
> around it? In such case, please post the mumbo-jumbo.
Yep, the error is just "row handle invalid", it is sometimes accompanied
by another error 'you tried to access a record which has been, or is
currently marked for deletion'
Cheers for your help,
Chris|||Not Me (not.me@.nowherefake.addr3s.com) writes:
> Yep, the error is just "row handle invalid", it is sometimes accompanied
> by another error 'you tried to access a record which has been, or is
> currently marked for deletion'
Sound like Access messages to me, so I would recommend trying an
Access newsgroup. Those are not messages from SQL Server.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
No comments:
Post a Comment