That is interesting.
Do you use visual class libraries, or define your classes in a prg?
I have always put related stuff into a single library, what is your reasoning for multiple libraries?
Given the reference you gave earlier, I assume you are familiar with VMP.
Would you create multiple intermediate libraries based on the multiple class VMP libraries?

>That's a relief! Consider also not putting more than one class in a class library. I think the only exception I'd use there is if the one class is a compound class and the components are subclassed to be part of the one class.
>
>>Hi Mike,
>>
>>I did not make myself clear so let me clarify.
>>I do not put my library routines in a common physical file, unless I am creating classes and put them in a class library.]
>>
>>In cases like this, I will have an individual prg for each pdf, then put of all my utilitiy prg's in a 'library' as in
>>

c:\dev\libs

This folder (library) is then added to my path, so I actually meant what you are saying, I just did not say it well.
>>
>>Burt
>>
>>>Hiya Burt!
>>>
>>>That's something I want to disagree on. Worry about what happens at runtime. Copying the files around is not even a design time issue. It's more of a setting up the development environment. You only need to set the path so VFP can find the prgs. As you said, the project manager will pull in everything.
>>>
>>>Take a look at this...
>>>
>>>http://fox.wikis.com/wc.dll?Wiki~VFPSetProcedure~VFP
>>>
>>>>You certainly have a point on the 'I forgot to copy the file' issue.
>>>>What I due is have a central library for my utility code that I include in the path for all of my projects. When I build the project, if the UDF is referenced, it will automatically be pulled into the exe or app file.
>>>>The only place I would really see this biting me would be if I was running from a command window without the utility library available.
>>>>
>>>>
>>>>>Hi Burt, Hi all,
>>>>>
>>>>>>DTOS() is easier to read than DTOC(,1)
>>>>>
>>>>>>To Preserve consistency, what I would do is create the following function
>>>>>>Function TTOS(tdDate)
>>>>>>Return TTOC(tcDate,1)
>>>>>
>>>>>I'd prefer #DEFINE, if you could do some define like
>>>>>

>>>>>#DEFINE TTOS(a) TTOC(a,1)
>>>>>

>>>>>but that doesn't even work with a=DateTime().
>>>>>
>>>>>Consistency advantage and readability or not, with a function or a define you are dependant of that and if you forget to copy that function or define into your next database stored procs, you'll also run into errors. So I'd say use DTOC(dField,1) in the key expression and TTOC(tField,1) with DateTime fields. It's not all that hard to look up or just try out the meaning of ,1 in the command window.
>>>>>
>>>>>Bye, Olaf.