You can only create meanginful relations in the mdb file that contains the
actual tables. If you try to do so in the front end, you are doing no more
than drawing lines. Referential integrity is not available.
What we do for developing is to build the entire database: tables,
relations, forms, queries, reports, and code. Then when everything is in
place, split the database. If there are any structural changes after this,
open the back end, and change the tables/relations/indexes there. The
changes in the back end are reflected in the front end.
One other factor that can cause considerable frustration is Name
AutoCorrect. It tries to track changes to the table/field names, but it can
get thoroughly confused and mess up the display of relations as well as
other more significant problems such as corrupting your database. Make sure
the Name AutoCorrect boxes are unchecked in both the back end and the front
end under:
Tools | Options | General
More info:
http://members.iinet.net.au/~allenbrowne/bug-03.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Sukkel" <am**********@y ahoo.com> wrote in message
news:11******** **************@ c13g2000cwb.goo glegroups.com.. .
When I define relations in the Backend of my Database, everything works
fine. I get these funny lines (with 1 and "OO") between the fields of
the different table that indicate a one to many relationship.
Then, when I try to build a query in the frontend, these signs
disappear in the query design window, and as a consequence, the form
wizzard based on such a query won´t let me construct a subform in the
main form.
I could make my queries and forms in the backend, and then import them,
but I just don´t like to do that (yet). I want to know what is going
wrong here....
Hope I could make my case clear....
Thanks for any reaction