Table Paths

[Al Smith]

Is it possible to save tables, forms, queries, etc, in different sub-folders,
within a database file, e.g. - Patient database in My Documents/Patients;
Vacinations in My Documents/Patients/Vacinations, etc?

Hope I made myself clear.

Thanks in advance.

Al

 

[tina]

an Access database is one file that is saved to one place on your computer
or network. the tables, queries, forms, reports, macros, and modules are
*objects* within that one file. you CAN use one or more tables from database
file A in database file B - by creating links to specific table objects from
database file A, within database file B. other than that, i think the short
answer to your question is No.

if you can explain *why* you want to store different database objects in
different places, perhaps we can suggest one or more solutions that will
fulfill your underlying purpose.

hth

 

[Al Smith]

My desire is just for housekeeping purposes. There will be many tables,
forms, queries, etc., and I was just interested in keeping tables and related
forms, etc together. Just something I think would be easier to navigate.

Thanks for the reply.

Al

 

[John Vinson]

My desire is just for housekeeping purposes. There will be many tables,
forms, queries, etc., and I was just interested in keeping tables and related
forms, etc together. Just something I think would be easier to navigate.

In Access 2002 and later (I believe that's where it came in), you can
select Edit... Groups... New Group on the menu while a database tab is
visible. This will let you create folders within the Tables, Queries
or other categories.

John W. Vinson[MVP]

 

[tina]

well, you're welcome. John's response gives you just what you're looking
for, i think - and the objects are all within the single database file. i've
never used object groups in a database before, but i tried it out in an
A2000 format db created in A2003. works very nicely - too bad my current
project is restricted to A97, or i'd put groups to use myself.

 

[Tim Ferguson]

There will be many tables,
forms, queries, etc., and I was just interested in keeping tables and
related forms, etc together. Just something I think would be easier
to navigate.

Some things _have_ to be in the same file: the tables and the relationships
(and, arguably, perhaps some very common and useful querydefs).

All the other things, like reports and forms, belong in different file(s).
These should be grouped in terms of functions or users: you might have a
ClinicClerkRegistration.mdb with all the record creation/ updating forms in
it; the NursingProcess.mdb with forms for recording how many bandages were
used up or thrown away; a SeniorManager.mdb with read-only access to
summary reports; and so on.

Of course, the sensible place to put each of these is on the workstation
local hard-disk, while the backend mdb lives on a central server.

Hope that helps


Tim F