Splitting the Database

[Boon]

I am trying to use the UNC path when I split the database by using the
splitting wizard.

Every time I did it, Access points to the backend by the X:\, the path that
I mapped in my network drive.

How can I tell Access to point to by UNC path?

thanks.

 

[John W. Vinson]

I am trying to use the UNC path when I split the database by using the
splitting wizard.

Every time I did it, Access points to the backend by the X:\, the path that
I mapped in my network drive.

How can I tell Access to point to by UNC path?

thanks.

In either the Linked Table Manager, or in File... Get External Data... Link,
navigate to your backend via Network Neighborhood (or whatever it's called in
your version of Windows), rather than through the "My Computer" file
heirarchy.

I don't believe the wizard will do this but you can reset it after the initial
split. You'll probably want to move the backend, and certainly the frontend,
in any case.

 

[Golfinray]

Use the tools/database utilities/linked table manager. Check the box for ask
for new location. When it asks for new location, select the location of each
table and it should update.

 

[Douglas J. Steele]

Don't know about using the wizard (I've never seen a need for it), but if
you go through the Linked Table Manager, you search for the back-end
database through Network Neighborhood (or whatever it's call in your OS),
rather than searching via the mapped drive.

 

[Boon]

Thank you for all the answers.

I have another following question.

I have two tables that related to each other. (Relationship). Let's say
that Table A is the mother table and table B is the child table. When I open
table A in the front-end, I couldn't see the plus sign at the first section
of each record. I can see the plus sign when I open the back-end though. Why
I don't see it on the front-end? Am I be able to see it?

thanks,

 

[John W. Vinson]

Thank you for all the answers.

I have another following question.

I have two tables that related to each other. (Relationship). Let's say
that Table A is the mother table and table B is the child table. When I open
table A in the front-end, I couldn't see the plus sign at the first section
of each record. I can see the plus sign when I open the back-end though. Why
I don't see it on the front-end? Am I be able to see it?

This is a bit confusing... Table A is in the mother table? Do you mean
database?

Relationships can only be established and enforced between tables *in the same
database*. Normally all of the tables will be in the backend .mdb file, and
all relationships will be established there. Access cannot enforce
relationships between different databases, because it has no way to control
what's happening in some OTHER database - if you have a relationship between
TableA in Front.mdb and TableB in Back.mdb, established in Front.mdb, there's
no way to prevent someone opening Back.mdb by itself, or from a third
database, and changing the contents of the table in a way that violates the
relationship.

Do note that Subdatasheets - the + sign - are a major drag on performance, and
are *NEVER* necessary. You shouldn't be using Table datasheets to work with
data in any case - you should always use a Form (with subforms) for
interaction with the data.

 

[Boon]

Thanks,

The table A and B are both in the back-end. When I open table A from the
front-end, I cann't see the plus sign. I can see the plus sign when I open
the table A from The back-end.

thanks,

 

[John W. Vinson]

Thanks,

The table A and B are both in the back-end. When I open table A from the
front-end, I cann't see the plus sign. I can see the plus sign when I open
the table A from The back-end.

If you really want the poor performance, bad user interface, and risk of
corruption, open the parent table in the frontend in design view. Access will
warn you that it's a linked table and you can't change some features; click
ok. View its Properties and change the Subdatasheet property from [None] to
either [Auto] or to the name of the table that you want as the subdatasheet.

I'd still recommend that you not do so, but it's your database!