Linking External Tables

[OldBirdman]

You are right, I have no real interest in networking at this time. I personally have 2 machines (maybe 3 if I count the one that is failing). My companion has one, and only uses a few of my programs.

Windows XP uses a different file structure than Vista, and the default user folders have different names. Anything in these folders can never match.

The new laptop intends that I do not use the C:\ drive, but that all my data be on D:\ but if I do that, nothing can match as D:\ on the other possible machines is the CD Drive.

So now I have a folder "_OldBirdma n" on all machines. I've never used that name for anything else except forums, so no conflicts. Leading underscore(_) puts it first in file manager.

Vista Sync (to keep files syncronized) doesn't work between XP and Vista computers, but Microsoft SyncToy does. This program will copy any changed files to the other computer, if (and only if) both are not changed since the last Sync.

So, yes, I've gone as far as I want to with this, at this time.

[NeoPa]

So, yes, I've gone as far as I want to with this, at this time.

Sounds good OB. If you're good then we're good :)

I'll just point out another item though, for the benefit of anyone else reading the thread.

Using Computer Management (found in Administrative Tools) you can select Storage / Disk Management and change the drive letter used for your CD or DVD drives.

Using SUBST, you can also make up another virtual drive from an existing folder.

These tools can give extra flexibility if required.

[ADezii]

I've just performed a cursory reading of this Thread so forgive me if I do not interpret this correctly. Couldn’t a Table exist in each Front End with the Table Names to be Linked as well as their Absolute Paths. It would then be a simple matter to programmaticall y Delete the existing Links, then re-create them reading the proper values from the Table. Am I oversimplifying , or have I missed the point altogether?.

[DonRayner]

Using Computer Management (found in Administrative Tools) you can select Storage / Disk Management and change the drive letter used for your CD or DVD drives.

You can also get to Computer Management by right clicking on the My Computer Icon and selecting Manage.

[OldBirdman]

Couldn’t a Table exist in each Front End with the Table Names to be Linked as well as their Absolute Paths

Yes, it could, but that absolute path would have to be the same on all computers involved. If that were true, then the table would not be needed, because if the absolute paths were identical, Access would intepret the links as valid, so it would not have to be re-linked.

Using Computer Management (found in Administrative Tools) you can select Storage / Disk Management and change the drive letter used for your CD or DVD drives.

Using SUBST, you can also make up another virtual drive from an existing folder.

I see that I could move E: to F: then D: to E: so I could create a partition named D: which could exist on both of my machines. I could then put my back-end tables in a fixed location on D: and as long as I didn't use the Documents folder or other pre-defined folder on either machine, I could always have the tables at a fixed name, for example D:\OldBirdmanTa bles.
Is there an advantage of doing it this way, instead of putting the tables in the root directory of the C: drive of any machine, any configuration, any operating system?

[NeoPa]

I see that I could move E: to F: then D: to E: so I could create a partition named D: which could exist on both of my machines. I could then put my back-end tables in a fixed location on D: and as long as I didn't use the Documents folder or other pre-defined folder on either machine, I could always have the tables at a fixed name, for example D:\OldBirdmanTa bles.
Is there an advantage of doing it this way, instead of putting the tables in the root directory of the C: drive of any machine, any configuration, any operating system?

As a system administrator, I avoid two things (related to this question).

1. Putting anything in root folders that aren't necessary there.
2. Putting data on the system drive if you have multiple drives.

1. The root folder of any drive is involved in every file-open access, or any access where the location of a file is sought or searches are done. Adding a single file won't make searching in the root appreciably slower, but when you consider how many operations it affects, then keeping things out of there starts to seem more sensible.
2. On similar lines, if you have multiple drives, then having a dedicated system drive can help with performance. The less data clutter you have in there slowing down accesses the system needs, the less performance degradation you will have (at least from that cause).

I don't know how important you would see these issues, but now you know what it's about, you can decide for yourself whether to take or leave.

I can certainly see that using the C: drive for your situation would be the most straightforward (although an OldBirdmanTable s folder would make management easier too).

PS. Possibly irrelevant, but I always set any CD / DVD drives to letters starting from R: whenever I build a PC. That way the early drive letters are available for use when necessary.