Hi Mike,

I do totally agree with you...
I know that there are more than 5 versions for Gdiplus.dll, and they're not backwards compatible in all cases, so that means that replacing to a newer version not always will bring the same desired results.

This is why I want to know exactly which of all available GDI+ versions VFP calls first.

Note that HELP says:

To ensure that you use the correct copy of GDIPLUS.DLL, use the syntax IN GDIPLUS.DLL with no explicit path in your DECLARE DLL statements. For more information, see DECLARE - DLL Command.

So, they tell us to leave for VFP to decide alone which version will be used.
The problem is that there are some very few times when VFP might choose the wrong ??? version...




>I am wondering what possible problems this may cause. There are more and more programs that uses GDI. If you delete all other versions on the system, would this cause another problem in another application? I think the wisest solution is what the help suggests, in your declare use a implicit path.
>
>
>
>>In VFP9's Help, on topic "Using GDI+ in Reports" it is said:
>>
>>To ensure that you use the correct copy of GDIPLUS.DLL, use the syntax IN GDIPLUS.DLL with no explicit path in your DECLARE DLL statements. For more information, see DECLARE - DLL Command.
>>
>>I don't know why, but in some situations, specifically when creating Gradients with GDI+, some machines return a black Brush instead of a Linear Gradient.
>>This happens in very few machines.
>>
>>I've seen this problem only in 3 cases, and that was solved when I asked users to eliminate one by one the GDIplus.dll versions in their machines... Suddenly everything started to work as desired. That has happened in WinXP professional and in Win98.
>>
>>The problem remained even having a brand new version on the VFP's folder, on the app folder...
>>
>>What's the version that VFP9 uses by default ?
>>Where's the default location that it searches first?
>>
>>Thanks in advance
>>
>>Cesar