A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Missing Relationships



 
 
Thread Tools Display Modes
  #1  
Old September 17th, 2008, 09:09 PM posted to microsoft.public.access.tablesdbdesign
Laura
external usenet poster
 
Posts: 458
Default Missing Relationships


I have an Access 2003 FE/BE application. I have password protected my
backend database. When I link the tables on my front end I should be able
to go to Relationships and Show all relationships from the back end database.
It shows me nothing. When I look in the Linked Table Manager, I see a
checkbox, an arrow, ?, table name, path of database. If I try to refresh
the link and prompt for new location it shows MSAccess() as file type instead
of the normal Microsoft Access(*.mdb) file type.

My concern is that the relationships on the Back end are not being enforced
on the front end because of the inability to show the relationships. The
person that created this database did not name the keyed fields the same
across tables. So for example in the Program table the primary key is
called ID, in the related table it is called ProgramID. So when creating
queries the query window assumes that the ID field in the Program table is
related to the ID field in the Related table.
  #2  
Old September 18th, 2008, 12:14 AM posted to microsoft.public.access.tablesdbdesign
Tony Toews [MVP]
external usenet poster
 
Posts: 3,776
Default Missing Relationships

Laura wrote:


I have an Access 2003 FE/BE application. I have password protected my
backend database. When I link the tables on my front end I should be able
to go to Relationships and Show all relationships from the back end database.
It shows me nothing. When I look in the Linked Table Manager, I see a
checkbox, an arrow, ?, table name, path of database. If I try to refresh
the link and prompt for new location it shows MSAccess() as file type instead
of the normal Microsoft Access(*.mdb) file type.


View the relationships in the BE. From what little I can recall when
I've tried this in the FE things were screwed up and wasn't in my neat
and tidy format.

My concern is that the relationships on the Back end are not being enforced
on the front end because of the inability to show the relationships.


No, not being able to see them in the FE has nothing to do with how
the BE has them.

The
person that created this database did not name the keyed fields the same
across tables. So for example in the Program table the primary key is
called ID, in the related table it is called ProgramID. So when creating
queries the query window assumes that the ID field in the Program table is
related to the ID field in the Related table.


The fields that I use in my relationships are never named the same
either. Indeed no field in any table is ever named the same as any
field in any other table.

For example I might have tJobID linked to jID which is the Transaction
table JobID field linked to the ID on the Job table. And they work
just fine.

Tony's Table and Field Naming Conventions
http://www.granite.ab.ca/access/tablefieldnaming.htm

I'd investigate the relationships in the BE first. Doesn't sound like
they're setup properly.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
  #3  
Old September 18th, 2008, 03:25 PM posted to microsoft.public.access.tablesdbdesign
Laura
external usenet poster
 
Posts: 458
Default Missing Relationships

Tony,

I can see the relationships in the Back end and they work just fine there.
If I take password protection on the database off and link the tables to the
Front End. I can go to the relationships window and see all my
relationships and yes they are not neat and tidy as they are in the backend
but they are there and I can see them. The problem happens only when I
password protect the Back End database. When I do that and link the tables
(using the password) in the Front End, go to the relationships window, click
show all relationships and nothing appears.

Laura

"Tony Toews [MVP]" wrote:

Laura wrote:


I have an Access 2003 FE/BE application. I have password protected my
backend database. When I link the tables on my front end I should be able
to go to Relationships and Show all relationships from the back end database.
It shows me nothing. When I look in the Linked Table Manager, I see a
checkbox, an arrow, ?, table name, path of database. If I try to refresh
the link and prompt for new location it shows MSAccess() as file type instead
of the normal Microsoft Access(*.mdb) file type.


View the relationships in the BE. From what little I can recall when
I've tried this in the FE things were screwed up and wasn't in my neat
and tidy format.

My concern is that the relationships on the Back end are not being enforced
on the front end because of the inability to show the relationships.


No, not being able to see them in the FE has nothing to do with how
the BE has them.

The
person that created this database did not name the keyed fields the same
across tables. So for example in the Program table the primary key is
called ID, in the related table it is called ProgramID. So when creating
queries the query window assumes that the ID field in the Program table is
related to the ID field in the Related table.


The fields that I use in my relationships are never named the same
either. Indeed no field in any table is ever named the same as any
field in any other table.

For example I might have tJobID linked to jID which is the Transaction
table JobID field linked to the ID on the Job table. And they work
just fine.

Tony's Table and Field Naming Conventions
http://www.granite.ab.ca/access/tablefieldnaming.htm

I'd investigate the relationships in the BE first. Doesn't sound like
they're setup properly.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

  #4  
Old September 19th, 2008, 02:00 AM posted to microsoft.public.access.tablesdbdesign
Tony Toews [MVP]
external usenet poster
 
Posts: 3,776
Default Missing Relationships

Laura wrote:

I can see the relationships in the Back end and they work just fine there.
If I take password protection on the database off and link the tables to the
Front End. I can go to the relationships window and see all my
relationships and yes they are not neat and tidy as they are in the backend
but they are there and I can see them. The problem happens only when I
password protect the Back End database. When I do that and link the tables
(using the password) in the Front End, go to the relationships window, click
show all relationships and nothing appears.


Interesting. I've never used Access security so I don't have a clue.
I'd suggest asking in the m.p.access.security newsgroup as a few good
folks understand security and hang out there.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 06:42 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.