Sorting attached table gives errors 3000, 3011 (can't find MSysAccounts)

  • Thread starter Thread starter Rob at RSD
  • Start date Start date
R

Rob at RSD

I have a split database that I developed in A2000 and
execute in A2002. While under A2002, I applied a sort to
an attached table in the code database. After doing so,
when I tried to open the code database, I got a long delay
and eventually one of two errors:

Error 3000: (no message assigned), or
Error 3011: "The Microsoft Jet database engine could
not find the object 'MSysAccounts'. Make sure the object
exists and that you spell its name and the path name
correctly."

Seems weird to me that a sort should corrupt the linkage
to MSysAccounts. Anyone else observe similar behavior?

TIA,

Rob (at RSD)
 
"Applied a sort to a table"? A relational database table, by definition, is
unordered. The only application of a sort in Access that I know about is in
a Query or in a Form or Report. Could you clarify?

Larry Linson
Microsoft Access MVP
 
Larry, thanks for the reply. I understand lack of
ordering in relational theory. It doesn't appear that
Access is following the theory here. When I have a table
open and sort on a column, it asks me if I want to save
the change in design. It does appear that the sort gets
saved as part of a filter applied to the table. The
problem I describe below occurs when I save the sort on a
table in 2002 in a database that has been created in 2000.

The same steps do not produce an error when executed under
the database's native platform - Access 2000. Could the
error be a byproduct of the deveoper's not handling a
filter without a WHERE criteria across versions?

Thanks again,

Rob
 
When I have a table open and sort on
a column, it asks me if I want to save
the change in design. It does appear
that the sort gets saved as part of a filter
applied to the table.
Click to expand...

Well, saving a filter to be applied when data is displayed is not quite
"ordering the data in the table". And, clearly, one could not save changes
to the design of an attached table.
The problem I describe below occurs
when I save the sort on a table in 2002
in a database that has been created in
2000.
Click to expand...
The same steps do not produce an error
when executed under the database's native
platform - Access 2000.
Click to expand...

I don't have Access 2000 on this machine to try to see if I can reproduce
the problem. But I created a table in Access 2002, saved in Access 2000 file
format, created a "front end" that linked that table in Access 2002, saved
it in Access 2000 file format. And, from Access 2003, no matter what kind of
column sorts I apply and "save", I don't encounter the error you describe.
It's possible that it is strictly an Access 2000-related issue, or it's
possible that it is an issue due to something else in your configuration.
Could the error be a byproduct of the
deveoper's not handling a filter without
a WHERE criteria across versions?
Click to expand...

I'm sure it _could_, but I don't know that it _is_. For me to try to assign
a cause would be nothing but idle speculation.

Larry Linson
Microsoft Access MVP
 
Back
Top