Can Built-in Access Forms Be Modified?

[Dave]

I suspect the title of my original post on this is being interpreted
as SPAM or something, because I'm sure there are a lot of very
knowledgable posters who would otherwise reply. Sorry if this seems
like cross-posting, but I cannot edit the original post. Here's what
was written with Wiztool as the subject (more or less):

Does anyone know if an updated version of Wiztool80 is available (we
are using Access 2002)? For those not familiar, Wiztool80 was an
unsupported MS download that allowed you to customize some built-in
forms such as the linked table manager. I had my own version of the
LTM in which I could actually read the entire network path for linked
tables. I'd like to have that back, as well as one in which I can see
the entire path for db references.

Thanks.

 

[Arvin Meyer [MVP]]

Why don't you just build a database of your own custom forms and use those
as a template:

Tools >>> Options >>> Forms/Reports

and specify your template form's name (reports too)

 

[Dave]

Why don't you just build a database of your own custom forms and use those
as a template:

Tools >>> Options >>> Forms/Reports

and specify your template form's name (reports too)

I've done so before as a basis for all forms within a project, but not
like I think you're suggesting. If I understand you correctly, you're
suggesting this as a solution for not being able to see the entire
path in the linked table manager or project references form (in the
VBA editor) that are built in to Access, and that by doing so I can
maintain the operability of those built-in forms? If so, I surmise I
would have to replicate the code that for example, opens a file path
dialog, iterates through a set of tables and re-links them according
to the chosen path. That would be bad enough for my level, never mind
deciphering collections of GUID's for references! Or did I
misunderstand you?
Hope you can clear this up for me.
Thanks.

 

[Arvin Meyer [MVP]]

I've done so before as a basis for all forms within a project, but not
like I think you're suggesting. If I understand you correctly, you're
suggesting this as a solution for not being able to see the entire
path in the linked table manager or project references form (in the
VBA editor) that are built in to Access, and that by doing so I can
maintain the operability of those built-in forms? If so, I surmise I
would have to replicate the code that for example, opens a file path
dialog, iterates through a set of tables and re-links them according
to the chosen path. That would be bad enough for my level, never mind
deciphering collections of GUID's for references! Or did I
misunderstand you?

I think you misunderstood. The simplest path is usually the best. Just
import the forms from a template database.