If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Front End Linked tables
Hello,
I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks |
#2
|
|||
|
|||
Front End Linked tables
Although Access tables look a little like spreadsheets, having users
'mucking about' in the tables is a very good way to end up with very bad data. Access tables store data, Access forms display data. Use the forms, Luke! I'm having trouble visualizing 'going directly to the table' then 'entering data into [the link] table. More information, please... Regards Jeff Boyce Microsoft Office/Access MVP "Diggsy" wrote in message ... Hello, I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks |
#3
|
|||
|
|||
Front End Linked tables
Diggsy,
Well, first thing let's get them UNused to that. You really don't want your end-users doung anything in the tables. SOUNDS LIKE you have mapped your FE-BE but it's not the same on everyone's machine. I would suggest using UNC mapping. Now, if that is not your problem really going to need more informatio. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Diggsy" wrote in message ... Hello, I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks |
#4
|
|||
|
|||
Front End Linked tables
On Tue, 29 Sep 2009 15:01:04 -0700, Diggsy
wrote: Hello, I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks Then your frontend needs some more work! They should - MUST, I'd say! - have Forms (a Form for the parent table, one or more Subforms for the child tables), with appropriate textboxes, combo boxes, and other data entry tools to make it both easier and more controllable to enter data. They should NOT be editing tables at all, and *especially* not entering foreign keys manually into child tables: shudder!!! -- John W. Vinson [MVP] |
#5
|
|||
|
|||
Front End Linked tables
I Guess what I was trying to say that in the backend you can physically see
the linked connections by clicking the "+" in the table. By doing that it will open data from a linked table that is connected to that primary key. In the front end when you open the table it just shows that particular table only. I guess this may be normal since the data is physically in the back end and this could be resolved with Forms "Gina Whipp" wrote: Diggsy, Well, first thing let's get them UNused to that. You really don't want your end-users doung anything in the tables. SOUNDS LIKE you have mapped your FE-BE but it's not the same on everyone's machine. I would suggest using UNC mapping. Now, if that is not your problem really going to need more informatio. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Diggsy" wrote in message ... Hello, I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks |
#6
|
|||
|
|||
Front End Linked tables
Diggsy,
Yes that is true BUT you can do form/subform scenario to achieve the same thing. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Diggsy" wrote in message ... I Guess what I was trying to say that in the backend you can physically see the linked connections by clicking the "+" in the table. By doing that it will open data from a linked table that is connected to that primary key. In the front end when you open the table it just shows that particular table only. I guess this may be normal since the data is physically in the back end and this could be resolved with Forms "Gina Whipp" wrote: Diggsy, Well, first thing let's get them UNused to that. You really don't want your end-users doung anything in the tables. SOUNDS LIKE you have mapped your FE-BE but it's not the same on everyone's machine. I would suggest using UNC mapping. Now, if that is not your problem really going to need more informatio. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Diggsy" wrote in message ... Hello, I recently split my DB into a FE and BE. When I distributed the FE to the users ....there was a complaint that they can't see the links between tables. They were used to going directly to the table Entering the data and then clicking the linked table and entering data into that table as well. I noticed you can only do that by going into the BE DB. Is there a way to do this on the FE as well Thanks |
#7
|
|||
|
|||
Front End Linked tables
John W. Vinson wrote:
Hello, [quoted text clipped - 6 lines] Thanks Then your frontend needs some more work! They should - MUST, I'd say! - have Forms (a Form for the parent table, one or more Subforms for the child tables), with appropriate textboxes, combo boxes, and other data entry tools to make it both easier and more controllable to enter data. They should NOT be editing tables at all, and *especially* not entering foreign keys manually into child tables: shudder!!! And if you don't believe us, try summarizing your data (the whole reason it's in the database to begin with, right?) if users enter data through tables, not forms. BIG BIG mess. Been there, done that. If you really want to go that route, stock up on tylenol, because you're gonna need it! -- Message posted via http://www.accessmonster.com |
#8
|
|||
|
|||
Front End Linked tables
Diggsy wrote:
I Guess what I was trying to say that in the backend you can physically see the linked connections by clicking the "+" in the table. By doing that it will open data from a linked table that is connected to that primary key. That's called subdatasheets. But as others have suggested we strongly urge you to create forms and subforms. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/ |
Thread Tools | |
Display Modes | |
|
|