Hmm, Nick,
I think that it might be but there is so much code that I'm not sure what it
all does and how to use it.
Perhaps if I define the need a bit more clearly:
I have a database that accesses hundreds of images that are stored in
normal windows folders (i.e. not in an Access Database). The main folder
structure is always identical but, on different computers it might be
located in a different 'root' directory - e.g. in one an image might be in:
"C:\Pictures\Images\Image1.jpg" and on another it's in:
"F:\Material\Images\Image1.jpg". I have created a parameter that is used by
the database: - in example (1) it would be "C:\Pictures\" and in (2) it
would be "F:\Material\". Whenever the code needs to access an image, it
prefixes the 'standard' folder structure with the parameter value. It works
very well and makes the database easily portable between machines. At
present, when it is added to a new machine, I have to add this 'root' folder
location manually - on some it can be very long (especially when in
C:\Documents and settings\XXX\My Documents....etc.!) and easy to miss-type.
What I wanted to be able to do was to have a File|Browse function in the
form where the database field is displayed so that I can navigate to the
appropriate folder and sort-of <press enter> and it will populate the field
in the parameter table with the 'root' value.
Sorry it's been such a long description but hopefully it will be a pointer
that will help you to give me an idea of how I could use the proposed code.
Thanks for your quick reply!
Michael.