Delete first record error with linked tables

[Jerry]

Hi all,

I'm running Access 2003 , and I've created a simple test database with two
tables. tblA has an AutoNumber field and a Text field. tblB has an
AutoNumber field, a Number (Long Integer) field to link to tblA's AutoNumber,
and a Text field. I've created a One to Many relationship between the
AutoNumber field in tblA and the Number field in tblB with Cascade Delete
Related Records selected. I then add some test records in tblA and some
related records in tblB.
When I open tblA, I get a subdatasheet type view where under each record
in tblA there is listed the related records in tblB (actually you may have to
click the "+" in the heirarchy tree to show the related records). If I
highlight the first record in tblA, and delete it, Access crashes with the
"Access has encountered an error" message. This only happens with the first
record, and it only happens if I expand the tree to show the tblB related
records first. That's right, if I just delete the first record before
expanding the view, it works as expected.
Can anyone shed some light on this or has anyone seen this? I've
duplicated it on two machines in my network as well as a computer from
another company with a different install source.

Thank you,
Jerry

 

[Clifford Bass]

Hi Jerry,

I can confirm that it is the case with Access 2003 SP3 on my machine.
Further, it is any record that is expanded. The problem does not exist in
Access 2007.

Clifford Bass

 

[a a r o n . k e m p f]

maybe you should try using a more reliable, enterprise-ready database
engine, like for example; SQL Server and ADP

 

[Jerry]

Clifford,

Thanks for confirming it. I can't find a thing about it in any of my
searches. I wonder why it happens on other records for you.

Regards,
Jerry

 

[Jerry]

Aaron,

I do use SQL Server when the application calls for it. But I'm developing
a simple database for which SQL Server is overkill.

Thanks,
Jerry

 

[GenlAccess]

Aaron,

I do use SQL Server when the application calls for it. But I'm developing
a simple database for which SQL Server is overkill.

Thanks,
Jerry

Jerry, aaron doesn't really know what he is talking about, and he doesn't
really care if you put in extra work. He's a victim of ADP addiction and SQL
Server worship obsession -- real-world logic just doesn't exist in his view
of things.

Gen'l Access

 

[Clifford Bass]

Hi Jerry,

You are welcome. Could be related to some minor Office update that you
have that I don't. Or the other way around. The fact that it is fixed in
2007 indicates that it probably is a known bug.

Clifford Bass

 

[a a r o n . k e m p f]

there's no such thing. SQL Server is easier to develop in than MS
Acess.

stop spreading lies, Jet crybaby.

-Aaron