Linked Tables

[Guest]

I have created an application and split it between a front end and back end.
However, I have discovered that the field properties of a field as shown in
the back end (looking directly at the tables) and in my front end are not
identical. (One shows it as a text box, the other as a combo box linked to
another table.) I have run Link Table Manager and it says the front and back
ends are linked up, the front end shows arrows by all of the tables and
indicates that "some properties cannot be modified".

How could this happen and how do I correct it?

Lloyd

 

[Jeff Boyce]

Lloyd

I suspect your backend table has a field defined as a "lookup" data type.
This data type stores one thing, but displays another (i.e., it does a
lookup).

For this reason, many folks (see this tablesdbdesign newsgroup) run into
many problems. Consider modifying the backend field to reflect the actual
datatype of the ID field in the (other) table being used for lookup.

Then use forms to do any lookups!

Good luck

Jeff Boyce
<Access MVP>

 

[Guest]

Thanks Jeff. I would have thought that looking at the table from the
frontend and backend would always show the same information.

Actually, my "issue" is different. The backend shows the field in the table
as a text box while the frontend show it as a combo box with a row source
type and row source defined. I want to use the combo box definition, should
I simply make that change in the backend?

Lloyd

 

[Jeff Boyce]

Maybe I'm interpreting what you've described.

When you say "the backend shows the field", where in Access are you when you
"show" it? And when "the frontend shows it as a combo box"...?

And I was suggesting AGAINST using a lookup field in a table definition.

Good luck

Jeff Boyce
<Access MVP>

 

[Guest]

I was clearly misinterpreting too!!

The "problem" that I discovered was that field definition of a particular
field in the backend (from Table Design) and the frontend (also from Table
Design) was different. I presumed that the field definitions provided to
the backend would be retained and enfoced in the frontend and feared that
this might be a serious consistency problem in my application. I think you
are telling me that Access allows such changes in the frontend, though you
don't recommend it. Is that correct?

And I did not follow my suggestion and change the value in the backend.
This part of the application seems to be working fine, I was just worried
about "down the road".

Thanks again, Lloyd

 

[Jeff Boyce]

Lloyd

If you have truly "linked" (not "imported") a table into a front-end, as far
as I know, you can NOT modify it. From what you've said, I therefore
suspect that you imported the table to the front-end, not "linked" to it.
In the front-end, does the table show with/without a small arrow to the left
of the name of the table?

My suggestion about lookup data types applies, period. Front-end, back-end,
"middle-end", they seem to cause more headaches than they cure. Check the
newsgroup for others' opinions.

Good luck

Jeff Boyce
<Access MVP>