Thanks John

I'm taking the do-it-yourself porting strategy for now .  I worked in an ISV multi-developer shop for 5+ years.  They had the PFC services porting work already done before I arrived.  Since it was a part of their enterprise application suite, even though they kept the comment headers in the code, they didn't share their "Out of Framework" Port with the general public.

I really thought that so many years downstream from OpenSource PFC, some group would have made generic type services publicly available.

Today, I spent a some time moving of_dirlist( ) into a POPO (plain Old Powerbuilder Object) NVO.  I'll likely do the same for each function as I need it.

Yakov

Yakov - 

Do you have a list of the File Service functions you need? If no one has exactly what you've asked for, it might be simpler to create an "equivalent" NVO with only the functions you need rather than convert all 60+ functions.

Do you need the external function declarations for the WinAPI calls to be 64-bit compatible (i.e., use Longptr datatype, etc.)?

How quickly do you need this?

Best regards, John

Thanks Chris,

This is very nice useful information which I have known about for years.   But OpenSource PFC doesn't address my immediate requirement

I'm looking for a *standalone* version of PFC file service (which are higher level wrappers onto Windows API calls) 

EXTRACTED from PFC.  (Yes it can contain all the opensource copyright notices)

I.E. You can use file services without the PFC PFE spiderweb of interrelated classes in a NON visual application run as a service

Yakov

Hi Yakov;

 FYI: http://github.com/OpenSourcePFCLibraries

Regards ... Chris