>Maybe it seems to you like I'm doing too much work, but if I follow your advice, I'll have to retrain for a little while first, and I just need you to point me in the right direction, first, please.
>
>So, where can I get some info on your commands and libraries and so on, please?
>
>\/\/\


Vernon,

Sorry, didn't mean to overwhelm you. The information that I
provided (the RegFNs) are Windows API functions. Since you're
using FPW, you need to register these functions using the RegFN
function in FOXTOOLS.FLL. If you can get your hands on a copy of
the Windows 3.1 SDK Help file (WIN31WH.HLP) you'll find
documentation on these, as well as all the other 3.1 functions.
Lacking that, I'd suggest the Microsoft Knowledge Base.

As far as FOXTOOLS goes, I think you might find FOXTOOLS.WRI in
the GOODIES\FOXTOOLS directory. If not, let me know.

What the RegFN function does is return (for lack of better
words) a handle to the function. The first parameter is the
function name, the second is a parameter list description: ("C" =
character, "I" integer, etc.). The third parameter is the return
data type. If the function is part of the API a fourth parameter
isn't needed. If it isn't you also supply the name of the DLL the
function is in.

Once you have the function handle, you use it to call the
function with CallFN() passing it the parameters as well.

GetProfileString retrieves a string from WIN.INI. There's a
similar function (GetPrivateProfileString) that retrieves a
string from other INI files.

WriteProfileString stores a string in WIN.INI. Of course, there's
also WritePrivateProfileString.

SendMessage is used to tell the other open applications to reload
the section modified by WriteProfileString. If you don't, then
the applications that are already open won't be aware of the
change (this includes FoxPro).

All you have to do to load FOXTOOLS.FLL is:

SET LIBRARY TO FOXTOOLS.FLL ADDITIVE

You may have to supply the path if the library isn't in the
default directory.

I think you'll find FOXTOOLS very handy. Besides the RegFN and
CallFN functions, there's MsgBox(), which is a hook into the
Windows MessageBox(). It allows you to call this function to
display a modal dialog with one of several button combinations,
and icons.

I said that I thought you were trying to do to much work because
it seemed liked the problem was one in which you'd want to have
complete programmatic control.

If I still haven't answered all your questions, just let me know.

Good Luck,

George