Hi. Have you tried adding a criteria to your dropdown?
this was an excel data entry b4. i tried defining field2 at table level as a drop down but that gave little wiggle room when i tried to add the conditionality at form design
field1 field2
anything anything
Customer DropDown
repeats down form
That's where I kinda flamed out, trying to set a conditional format rule, which kinda worked cept cud not get to the 2nd table with the dropdown values in it.Hi. Rather than do it at the table, try doing it on a form.
That's where I kinda flamed out, trying to set a conditional format rule, which kinda worked cept cud not get to the 2nd table with the dropdown values in it.
Also tried setting a CONTROL SOURCE clause for field2 but did not quite "compute". I guess the issue is figuring how to - "referring to" either the 2nd table or to the sql which creates it (the 2nd table).
Hi. Thanks. The attached just does what you asked for. I am not sure if this is going to be useful for you though.Here is the database
Hi. Maybe you can't, but we always recommend to use forms instead of editing data directly from the table. For example, your original request can't be done at the table level, so I suggested to use a form instead.I guess I do not see a lot of benefit from creating a form in Datasheet view - rather than just going directly to the table itself for data entry ???
That example scared me away cause when I entered data in field2 it appeared the same in every row on the form
Alas, I guess it is simply not possible to turn on or off a dropdown list in the same column of a form field ON A ROW BY ROW BASIS - based on the value of another field.
This is what Excel is: .... used for spacing
Field1.............Field2........Field3......etc., etc.
Rich...............SAT
.....................08/06/19
.....................IN.............OUT
Customer........Conery-1
Am................700............800
Pm
Customer
Am
Pm
etc.
etc.
Actually, that is another problem. Access is not the same as Excel. We don't recommend storing the data into tables like that. In database design, there is a principle we follow called Normalization. If you're more comfortable using Excel, then maybe you need to use Excel and save Access for later. Just my 2 cents...
I am fully aware of that, and that's how it works now (Excel is transferred over to Access Tables). However, I do see advantages to NOT have to have anything "to do" with the Excel side at all - So that's why the search for a "nearly" comparable solution - wholly within Access.