MU File Reference Library

[help_me_with_access]

well it sounds to me like you're giving up. if you want, why don't you tell me what the end goal here is? I can't even gather that...even after 15 posts in this thread.

what's the purpose of your job? and do you know how to get it done?

[dandoescode]

The end goal is to create a list of the necessary reference libraries for the various data types. The idea is to create a single version of the 35 databases currently in use, to do this we need to make sure that all required libraries are included. It would appear as far as I can tell that MUFile is not a type that anyone knows of, and likely was created by a programmer for one of the databases, this is supported by it only coming up once in over 10,000 lines of code. I will make note of this line, pass it on to my boss and see what is to be done about it.

[help_me_with_access]

it may also be relevant to understand terminology here too. data types are small memory placeholders that are used to hold values. they're not related to libraries, but directly related to the environment you're working in. libraries, unless i'm mistaken, are nothing more than sets of pre-defined construct directives that are compatible with various software programs and their environments, depending on if the environment can support the constructs. DLL and type lib information is used to tell the environment how to allocate memory, how much to use, and what operative extensions are available for the memory item. but I may be getting a little of the wall there...

but if you need a list of reference libraries to pass on to the next person, and all 35 of your databases are all access databases, why don't you just open up the database files one by one using a simple visual basic app and write down manually the references that you seen in all the visual basic projects?

probably 1 hour or less...DONE.