>>>
>>>Thanks for your answer.
>>>I tested the registry entries mentioned above, and I saw, that under NT and Win95 the values are different in type. The length of a font entry in NT is 92 byte long and font name is in two byte format. But under Win 95, the font name is in normal string format and the structure of the whole entry is, like You wrote. I know that NT internal character format is UNICODE. But is it good practice to write code, that differ depending on the OS type. And what if the next windows version use a different format?
>>>
>>>Any comment?
>>>
>>>BB
>>
>>Bela,
>>
>>You can use OS(1) to determine which version of Windows you're applications is running under, and design the program to react accordingly. Quite frankly, I don't know if there are any differences between NT 3.51 or 4 that might cause further differences. Perhaps, someone else here does.
>>
>>George
>
>Hi again!
>
>Yesterday night I consulted a C++ programmer who suggested me the SystemParametersInfo Win32 API function, that could solve my original problem independently the o.s. (either Win95 , or NT4.0) The problem is, that this function uses structures in structures to give information about fonts.
>How can it do under VFP? I read the article about passing and receiving structures to API functions, but I don't know how to uses structures in structures. Symply insert to the original structure string the string which equal to the embedded structure?
>
>BB

Bela,

While I've never done anything with embedded structures, I would think that inserting a string within another might. Unless, of course, the second structure is referenced by a pointer within the first. But a solution to this problem can be found here. Check out the POINTERS class, written by Paul Vlad Tatavu, in the download section (Win32 and other APIs). It's just what you need to solve a problem like this.

George