Implied/hidden query in DataSheet view?

C

colin_e

I have a table "Org". Fairly straightforward, other than the fact that it has
a foreign key relationship to an "OrgType" table through the OrgTypeID field.

1) When I open this table in datasheet view (default), I receive a prompt
for a
parameter named "ID".

a) It's not obvious to me how a TABLE (not a query) can have a parameter??
b) I have no objects or fields called "ID" anywhere in my database.
c) Whatever I enter at the prompt makes no difference, I always see the
full
table (as you would expect when opening a raw table)

2) In datasheet view I cannot rename fields in this table, because Access says
the table is in use (locked). This happens after quitting/restarting
Access or
even a full reboot. However if I switch to design view I can rename
fields.

It looks to me as if Access is somehow running an "implied query" (if such a
thing exists) when datasheet view is open, however I can find no information
in the help etc. as to exactly what is going on here.

Any pointers would be much appreciated.

Regards: Colin
 
J

Jeff Boyce

Colin

You asked for pointers...

Access tables hold data, Access forms display it. I'd recommend that you
stop trying to use tables to display data.
 
J

John Spencer

For Number 1

Open the table as normal
Click on Remove Filter/Sort
Close the table and save the changes
Open the table again
 
C

colin_e

Hmm, I have to say this is less than helpful. I wasn't trying to display
data, I was trying to design a table, which currently contains no data.

The Access datasheet view has the capability to alter field names. SOMETIMES
this doesn't work, and the error message is not helpful. I am trying to
understand why.

Colin
 
J

Jeff Boyce

Colin

I've very rarely used the datasheet view, so I'm not sure I can help with
why it would sometimes allow field name changes and sometimes not. I'm
certain I don't know what error message is being displayed.

If you open the table in design mode, click on View and click on Properties,
you should get a list of the table's properties. If the "Subdatasheet" is
set to [Auto], change it to [None].

Does that help?
 
C

colin_e

Oh, now I didn't realise lookup fields were a problem. They ARE a convenent
way of getting constrained "safe" input of a field into every form without
hand-crafting the same UI into every form. I will look at the info referred
to, thanks.

Regards: Colin
 
R

Randy Harris

colin_e said:
Oh, now I didn't realise lookup fields were a problem. They ARE a convenent
way of getting constrained "safe" input of a field into every form without
hand-crafting the same UI into every form. I will look at the info referred
to, thanks.

Regards: Colin
Click to expand...

Colin,

Use a lookup table, rather than a lookup field.
 
Top