Solved what the??

[John Sh]

The first image below is the detail of the table "Speciestemp" in the back end of a split database.
The second image is the same table in the front end showing the link detail. "J" is an external hard drive.
The third image is what happens after clicking the front end link of "Speciestemp".
I have tried removing all records from the table with the same result.
If I click on "OK" the table opens normally. If I click on "Cancel" it closes.
Edit.
In it's usual function, to hold a list of data, the table behaves correctly.

Why is this table acting like a query?

 

[The_Doc_Man]

Check the properties of the table. From your description, you have defined a property based on the word "Spelling" as though it was a property of the table. But since there is no native property called .Spelling, Access can't find it so thinks it must be a parameter.

 

[John Sh]

Check the properties of the table. From your description, you have defined a property based on the word "Spelling" as though it was a property of the table. But since there is no native property called .Spelling, Access can't find it so things it must be a parameter.

see attached images.
Note..
Opening this table in the back end does not generate the dialog.
.

 

[John Sh]

I have just done a copy, paste and re-link of my database and the "Speciestemp" table is gone.
There must have been some corruption in the table.
Just one more mystery to be pondered.

 

[The_Doc_Man]

Glad you got it to a usable state. That would be an odd bit of corruption because appending the name "Temp" to another table (i.e. your "Species" table) isn't a normal Access crash recovery action - unless Microsoft has changed things AGAIN.

 

[cheekybuddha]

Beware naming a table field as "Collection".

It's a reserved word in Access which *could* cause weird issues like you faced.

 

[GPGeorge]

It might have been a saved filter or sort on the table. It could be other things, but creating a new version cleared it up, so it's moot now.

 

[John Sh]

Glad you got it to a usable state. That would be an odd bit of corruption because appending the name "Temp" to another table (i.e. your "Species" table) isn't a normal Access crash recovery action - unless Microsoft has changed things AGAIN.

Speciestemp was my naming as its a temporary file to hold ephemeral data.

 

[John Sh]

Beware naming a table field as "Collection".

It's a reserved word in Access which *could* cause weird issues like you faced.

Good point. I hadn't thought of that. It only occurs a couple of times so easily changed.

 

[John Sh]

It might have been a saved filter or sort on the table. It could be other things, but creating a new version cleared it up, so it's moot now.

No filtering or indexing on the file, that's done in a query.
Where did you find that property sheet?

 

[GPGeorge]

No filtering or indexing on the file, that's done in a query.
Where did you find that property sheet?

It's in the design view of the table.

 

[John Sh]

Beware naming a table field as "Collection".

It's a reserved word in Access which *could* cause weird issues like you faced.

I have checked here, https://azlihassan.com/apps/articles/microsoft-access/general/access-reserved-words
and here, https://learn.microsoft.com/en-us/office/troubleshoot/access/reserved-words
and can't find "Collection" in either list although it would seem obvious that it should be reserved.