By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,656 Members | 801 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,656 IT Pros & Developers. It's quick & easy.

Relationships vanish

P: n/a
I have a FE, BE database on my home computer and a duplicate on the office
computer. Both use Ak2 on Windows XP. The one at home appears normal.

The BE consists of about 50 tables with numerous relationships and the FE 9
tables (fixed set up stuff) + the 50 linked table from the BE database. At
home on the relationship view I see all the tables and their relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship window
without the "_1" suffix as if the table were shown twice, so they apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating 2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks

Phil
Jun 27 '08 #1
Share this Question
Share on Google+
8 Replies


P: n/a
On Thu, 1 May 2008 22:03:16 +0100, "Phil Stanton"
<ph**@myfamilyname.co.ukwrote:

No idea what's going on. Are both systems on the same (latest) service
pack for Office? Do you have the latest video drivers (don't laugh;
sometimes this matters) installed?

-Tom.

>I have a FE, BE database on my home computer and a duplicate on the office
computer. Both use Ak2 on Windows XP. The one at home appears normal.

The BE consists of about 50 tables with numerous relationships and the FE 9
tables (fixed set up stuff) + the 50 linked table from the BE database. At
home on the relationship view I see all the tables and their relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship window
without the "_1" suffix as if the table were shown twice, so they apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating 2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks

Phil
Jun 27 '08 #2

P: n/a
Hi Tom

Both on SP3.

Haven't the foggiest about the drivers, will check later. This appears to be
a recent problem as I know, some weeks ago, all was OK, but there have been
a number of revisions of both BE and FE since then.

Am going to remove and re-install Office and see if that helps.

Thanks

Phil

"Tom van Stiphout" <no*************@cox.netwrote in message
news:nd********************************@4ax.com...
On Thu, 1 May 2008 22:03:16 +0100, "Phil Stanton"
<ph**@myfamilyname.co.ukwrote:

No idea what's going on. Are both systems on the same (latest) service
pack for Office? Do you have the latest video drivers (don't laugh;
sometimes this matters) installed?

-Tom.

>>I have a FE, BE database on my home computer and a duplicate on the office
computer. Both use Ak2 on Windows XP. The one at home appears normal.

The BE consists of about 50 tables with numerous relationships and the FE
9
tables (fixed set up stuff) + the 50 linked table from the BE database. At
home on the relationship view I see all the tables and their
relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship
window
without the "_1" suffix as if the table were shown twice, so they
apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships
for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating 2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks

Phil

Jun 27 '08 #3

P: n/a
"Phil Stanton" <ph**@myfamilyname.co.ukwrote in message
news:NbKdnaq1B-6bTIfVnZ2dnUVZ8qGdnZ2d@plusnet...
>
Am going to remove and re-install Office and see if that helps.
Before you do that, try your files on a different PC.

Regards,
Keith.
www.keithwilby.com

Jun 27 '08 #4

P: n/a
On May 1, 4:03 pm, "Phil Stanton" <p...@myfamilyname.co.ukwrote:
I have a FE, BE database on my home computer and a duplicate on the office
computer. Both use Ak2 on Windows XP. The one at home appears normal.

The BE consists of about 50 tables with numerous relationships and the FE 9
tables (fixed set up stuff) + the 50 linked table from the BE database. At
home on the relationship view I see all the tables and their relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship window
without the "_1" suffix as if the table were shown twice, so they apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating 2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks

Phil
I assume this is a secured database...are you using the same workgroup
file or an exact copy of it at home and at work?

Bruce
Jun 27 '08 #5

P: n/a
Tried files on Laptop and my home machine. All perfect

Re-installed Office 2000 on Office machine, and updated drivers. Problem
changed slightly that in the FE database all the FE tables show their links
as before, but now I can see all the BE tables. However there are no linking
lines between them.

Not all bad however. For example in the BE I have a table of Addresses and a
table of Towns (TownID being the PK in the Town Table and the FK in the
address table). If in the FE Db I add an address with a non existent TownID
I get the appropriate error message "You cannot add or change a record
because a related record is required in Table 'Town'"

It is as if the links are there, but not visible.

Phil
"Keith Wilby" <he**@there.comwrote in message
news:48********@glkas0286.greenlnk.net...
"Phil Stanton" <ph**@myfamilyname.co.ukwrote in message
news:NbKdnaq1B-6bTIfVnZ2dnUVZ8qGdnZ2d@plusnet...
>>
Am going to remove and re-install Office and see if that helps.

Before you do that, try your files on a different PC.

Regards,
Keith.
www.keithwilby.com

Jun 27 '08 #6

P: n/a
Hi Bruce.

This is not a secured Db. Actually I have never played around with
workgroups.
However. whether it is relevant or not I don't know, but I recently loaded
Sage payroll onto the office machine and that certainly uses Access and also
MDW files. I presume there is some significance to your question as the
problem seemed to occur at about the same time as I loaded Sage

Thanks

Phil
"Bruce" <de***************@gmail.comwrote in message
news:a3**********************************@26g2000h sk.googlegroups.com...
On May 1, 4:03 pm, "Phil Stanton" <p...@myfamilyname.co.ukwrote:
>I have a FE, BE database on my home computer and a duplicate on the
office
computer. Both use Ak2 on Windows XP. The one at home appears normal.

The BE consists of about 50 tables with numerous relationships and the FE
9
tables (fixed set up stuff) + the 50 linked table from the BE database.
At
home on the relationship view I see all the tables and their
relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship
window
without the "_1" suffix as if the table were shown twice, so they
apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships
for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating
2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks

Phil

I assume this is a secured database...are you using the same workgroup
file or an exact copy of it at home and at work?

Bruce

Jun 27 '08 #7

P: n/a
On May 2, 2:49 pm, "PhilOfWalton" <phil@stantonfamilywrote:
Hi Bruce.

This is not a secured Db. Actually I have never played around with
workgroups.
However. whether it is relevant or not I don't know, but I recently loaded
Sage payroll onto the office machine and that certainly uses Access and also
MDW files. I presume there is some significance to your question as the
problem seemed to occur at about the same time as I loaded Sage

Thanks

Phil

"Bruce" <deluxeinformat...@gmail.comwrote in message

news:a3**********************************@26g2000h sk.googlegroups.com...
On May 1, 4:03 pm, "Phil Stanton" <p...@myfamilyname.co.ukwrote:
I have a FE, BE database on my home computer and a duplicate on the
office
computer. Both use Ak2 on Windows XP. The one at home appears normal.
The BE consists of about 50 tables with numerous relationships and the FE
9
tables (fixed set up stuff) + the 50 linked table from the BE database.
At
home on the relationship view I see all the tables and their
relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship
window
without the "_1" suffix as if the table were shown twice, so they
apparently
aren't hidden somewhere. If I try to set up a relationship, the various
options are greyed out as I would expect as you can't edit relationships
for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End) Creating
2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks
Phil
I assume this is a secured database...are you using the same workgroup
file or an exact copy of it at home and at work?
Bruce
I was wondering if this might be a permissions related issue and I
suppose if Sage replaced the default system.mdw workgroup or joined
you to a new default workgroup it might be. You might try the
following:

On the computer at home, grab a copy of the system.mdw you're using
when you access your database (to find out where this file is, type ?
dbengine.systemdb in the VBA immediate window)

On the computer at work, open your database and use the same ?
dbengine.systemdb command in the VBA immediate window to find out what
workgroup file is being used when you access your database there.
Close Access. Rename that file and put the copy you brought from home
in the same location. Now look at your database again and see if you
can see your relationships.

Bruce
Jun 27 '08 #8

P: n/a
Hi Bruce

No dice. Both DBs are using the standard MDW file
(C:\PROGRA~1\COMMON~1\System\SYSTEM.MDW). I have replaced the office version
with my home version, but no change. Can see all the tables, but only the FE
tables show the relationships. Nothing appears unusual in the permissions.
(I don't think there is a permission to view relationships anyway)

Phil
"Bruce" <de***************@gmail.comwrote in message
news:f3**********************************@r66g2000 hsg.googlegroups.com...
On May 2, 2:49 pm, "PhilOfWalton" <phil@stantonfamilywrote:
>Hi Bruce.

This is not a secured Db. Actually I have never played around with
workgroups.
However. whether it is relevant or not I don't know, but I recently
loaded
Sage payroll onto the office machine and that certainly uses Access and
also
MDW files. I presume there is some significance to your question as the
problem seemed to occur at about the same time as I loaded Sage

Thanks

Phil

"Bruce" <deluxeinformat...@gmail.comwrote in message

news:a3**********************************@26g2000 hsk.googlegroups.com...
On May 1, 4:03 pm, "Phil Stanton" <p...@myfamilyname.co.ukwrote:
I have a FE, BE database on my home computer and a duplicate on the
office
computer. Both use Ak2 on Windows XP. The one at home appears normal.
>The BE consists of about 50 tables with numerous relationships and the
FE
9
tables (fixed set up stuff) + the 50 linked table from the BE
database.
At
home on the relationship view I see all the tables and their
relationships,
but on the office machine I see only the relationships between the FE
tables. Show all tables does nothing.
If I try adding the missing BE tables they appear in the Relationship
window
without the "_1" suffix as if the table were shown twice, so they
apparently
aren't hidden somewhere. If I try to set up a relationship, the
various
options are greyed out as I would expect as you can't edit
relationships
for
tables held in the BE DB in the front end.
Compact & Repair has dome no good (both Back End and Front End)
Creating
2
new DBs and importing everything has equally failed. Has Access gone
corrupt?
Thanks
>Phil
I assume this is a secured database...are you using the same workgroup
file or an exact copy of it at home and at work?
Bruce

I was wondering if this might be a permissions related issue and I
suppose if Sage replaced the default system.mdw workgroup or joined
you to a new default workgroup it might be. You might try the
following:

On the computer at home, grab a copy of the system.mdw you're using
when you access your database (to find out where this file is, type ?
dbengine.systemdb in the VBA immediate window)

On the computer at work, open your database and use the same ?
dbengine.systemdb command in the VBA immediate window to find out what
workgroup file is being used when you access your database there.
Close Access. Rename that file and put the copy you brought from home
in the same location. Now look at your database again and see if you
can see your relationships.

Bruce

Jun 27 '08 #9

This discussion thread is closed

Replies have been disabled for this discussion.