Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Relationships disappeared after user-level security and splitting?

Status
Not open for further replies.

MaddiMond

Technical User
Mar 28, 2005
76
US
When I created a database, I established all the right relationships between tables. After set-up of user-level security, after splitting tables to a backend, these relationships disappeared and are only visible in the queries that I created before user-level security etc. When I want to make a new query, I have to tell them the relationship again. Is that normal? Is that what happens when one does security and splitting or did something go wrong?
Thank you for all your valuable inputs.

Greetings,

Maddi
 
How did you split the database??
The relationships should be defined on the backend (where the tables are located).

When I split a database, I will import the forms, reports, queries into the front end. This way, the relationships are anot touched.
 
Had the same problem. All the foreign key relationships between tables gone after splitting database into front and backend. Would let me delete records from tables being referenced by other tables without any problem ??? Found no warning about this in the online help of MS. Luckily I had done a backup before because redefining all the relationships is just not an option.
 
This is how I solved the problem.

1. I made a copy of the database. Named it DatabaseNameBE.
2. Opened DatabaseNameBE. Threw away all my queries, forms, reports, macros and modules (ough!!). The database was only left with its tables (AND relationships between them!!!).
3. Compacted DatabaseNameBE.
4. Opened DatabaseName (the original)
5. Joined all the tables from DatabaseNameBE except the switchboard table. (They end up in the database under the name OriginalTableName1)
6. Deleted all the original tables (except switchboard).
7. Renamed all the joined tables to their original names by deleting the appended <1>.
8. Compacted DatabaseName.

I now have a database with a backend, where the referential integrity is still maintained. I cannot delete records that are referenced by records in other tables.

If anyone has a comment on why not to do it this way I would like to hear from you.

Regards drfreako
 
If you delete the unwanted ( real ) tables in the FrontEnd BEFORE you Get External Data and Link the tables to the BE then you won't have to do all that renaming.

Otherwise - Fine. But given the same single database to start with - I bet willir's approach will get you to the same result quicker. However, if your approach is more 'logical' in your mind - do it that way.





G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top