I currently have 2 Include files.  One is sbasic_include.sbas and the other contains a subroutine that Ray and Carl wrote to capitalize the initial letters of words entered in an element, cuInitialCaps_include.sbas.

Can I combine these two?  If so, can I just transplant the entirety of cuInitialCaps_include.sbas into sbasic_include.sbas?  If so, would its contents need to come before or after the #defines in sbasic_include.sbas?

You could combine them, but I think many of us are keeping our own codes out the file provided by Lantica.  This is in case they provide a newer/modified file in the future, that could overwrite the changes we had made to it. 

Wow fast responses, by the time I typed (answerd a phone call) and pressed post a lot had been said.



Infinity,

Many of us use 2 files

sbasic_include.sbas
mystuff_include.sbas

we keep all the stuff we create for ourselves in mystuff_include.sbas

when the lanticans make changes and additions to the sbasic_include.sbas you will not need to figure out what to add to the existing. You will be able to replace the entire file and not loose the stuff you created.

Mark, Erika, or Ray can probably tell us if this is not a good technique for some other reason, but it would seem to simplify updating.

I would actually suggest several files for custom functions not just one big one. Name them something descriptive such as

MyFormattingFunctions.sbas
MyPrintingRoutines.sbas
MyTrigFunctions.sbas
MyDancingMonkey.sbas

This way if you are working in say a report or a subform and you only need that one function that does the formatting of Money just the way you want it, you only have to include one smaller file rather than one large file. Compile times will be faster and in turn the report will run faster.

-Ray

Thanks again for the advice guys, I'll stick with multiple files for the reasons stated.

And Ray, please send me that code for the dancing monkey.