PB/CC - PB/DLL Compatability

[Scott Turchin]

I'm building a PB/CC app, all is well and I want to all a function in one of my basic DLL's that I use for everything (It tastes like chicken)..

Anyway, problem I am getting is that my INC file does the #include "win32api.inc" because of it's functions..

I do an #include "CCS.INC" and attempt to compile my app and get these errors about parameter mismatch with prior declaration...


I know there are differences between the two win32api.inc files...

I don't want to rewrite or cut and paste my code out, Be nice if I could just use it..

Is there a general solution to this problem, can I attempt to use the PB/CC win32api.inc with my CCS.INC ?


I can't seem to keep the two straight, my DLL is already compiled, therefore it should not need a win32api.inc or anything, my calls are all custom functions, therefore they should not need that either, but I do use some commctl functions and require that one....


Suggestions to proceed?

Scott

-------------
Scott Turchin

[Semen Matusovski]

Scott --
differences between two Win32Api.Inc are very small (compare by fc ... /C).
In PB/CC losted some declarations.
What really seems strange, that there are different ALIAS for some exotic functions (clear that correct is only one variant).
Which troubles do you see for using in PB/CC #Include "C:\PBDLL60\WinApi\Win32Api.Inc" ?

[Scott Turchin]

Initially I had some issues with the VariantTimetoSystemtime but I had made that change because my timeclock program was Dr Watson'ing on me, I put a Byval vbdate in it, that problem went away by specifying which win32api.inc to use.
Now, the CCS.inc has an include to the commctl.inc and the CreateWindow is returning the error...That may be an issue because as I understand PB/CC does not support DDT?

I think mostly this is a pathing issue at this point, but I'm still plugging away...

Scott

-------------
Scott Turchin