External Relationships not appearing in FE

[Guest]

First a little background:

I have been working with Access for about a year and a half; VB6/VBA for
about 3 years (started with GWBasic/Qbasic back in the dark ages). I don't
really have much professional training in either at this point. I am using
Access 2000 (which is my company's standard) to develop a database. I
successfully performed a manual split to a front end/back end setup (both
MDBs) some time ago, and things have been working pretty well until recently.
The front end accesses about 75 tables, around 60 of which are in the back
end. The rest are either local to the front end or linked from SQL Server
2000.

Now that that is out of the way, here is the problem:

The relationships that I set up in my back end are no longer appearing in
the front end after I have linked the tables. I need referential integrity
between most of these tables, so a local relationship isn't really an option.
I could probably come up with some kind of messy workaround, but I would
really prefer to resolve the issue directly.

I've attempted deleting the links, compacting the database and relinking the
tables, but this makes more bizarre results: The tables that I wanted to link
are now linked, but all of the links between those tables and other tables
have now disappeared from the front end.

I'm not sure if I have provided enough info; please inquire if you need more.

 

[Rick Brandt]

First a little background:

I have been working with Access for about a year and a half; VB6/VBA
for about 3 years (started with GWBasic/Qbasic back in the dark
ages). I don't really have much professional training in either at
this point. I am using Access 2000 (which is my company's standard)
to develop a database. I successfully performed a manual split to a
front end/back end setup (both MDBs) some time ago, and things have
been working pretty well until recently. The front end accesses about
75 tables, around 60 of which are in the back end. The rest are
either local to the front end or linked from SQL Server 2000.

Now that that is out of the way, here is the problem:

The relationships that I set up in my back end are no longer
appearing in the front end after I have linked the tables. I need
referential integrity between most of these tables, so a local
relationship isn't really an option. I could probably come up with
some kind of messy workaround, but I would really prefer to resolve
the issue directly.

I've attempted deleting the links, compacting the database and
relinking the tables, but this makes more bizarre results: The tables
that I wanted to link are now linked, but all of the links between
those tables and other tables have now disappeared from the front end.

I'm not sure if I have provided enough info; please inquire if you
need more.

Itr doesn;t matter. Relationships that appear in the front end are just "pretty
lines". If the relationships exist in the back end file then they are enforced
whether you see them in the front end or not.

 

[Guest]

Itr doesn;t matter. Relationships that appear in the front end are just "pretty
lines". If the relationships exist in the back end file then they are enforced
whether you see them in the front end or not.

Well that's a relief. At least I can continue working on this.

Still, any idea what might be causing this? It would be nice to be able to
see the relationships in the front end, at least for reference.

 

[Rick Brandt]

Well that's a relief. At least I can continue working on this.

Still, any idea what might be causing this? It would be nice to be
able to see the relationships in the front end, at least for
reference.

No idea. You can rebuild them in the front end (without enforcing) just for the
documentaton aspect.

 

[Guest]

Itr doesn;t matter. Relationships that appear in the front end are just "pretty
lines". If the relationships exist in the back end file then they are enforced
whether you see them in the front end or not.

 

[Guest]

I apologize for the blank reply. Stupid IE.

 

[Guest]

Itr doesn;t matter. Relationships that appear in the front end are just "pretty
lines". If the relationships exist in the back end file then they are enforced
whether you see them in the front end or not.

Well, the queries which involve the relationships in question have editable
recordsets, but every time I try to save a record, it gives me a "Could not
read the record; currently locked by another user." error. I know that the
record can't be locked by another user, because I am the only one accessing
either the FE or BE. Does this have anything to do with those relationships?
It only seems to affect the recordsets that depend upon them.

 

[Guest]

Nevermind. I just wasn't setting up the relationships properly in the query.
Dependency on access importing the relationship properties directly into new
queries has mentally handicapped me