Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
We have an old version of PFC, so...
41 views
Skip to first unread message
Rick
Apr 12, 2010, 4:53:17 PM4/12/10
to
We've just migrated our PB 9 PFC app to PB 11. In
pfc_n_cst_platformunicode, of_printdlg calls Local External Function
pfc_printdlg. I see that that Local External Function uses
pbvm90u.dll, and of course that now generates an error.
pfc_n_cst_platformunicode, of_printdlg calls Local External Function
pfc_printdlg. I see that that Local External Function uses
pbvm90u.dll, and of course that now generates an error.
I know my boss will never let us upgrade the PFC to a more recent
version. Given that, what are my options? Can I replace that with
something else? Thanks for any help.
Jeremy Lakeman
Apr 13, 2010, 2:43:35 AM4/13/10
to
just call PrintSetup() instead.
Rick
Apr 13, 2010, 11:17:39 AM4/13/10
to
Thanks much. I'm a bit slow to catch on to PFC --
In pfc_u_dw, event pfc_printdlg() I see:
ll_rc = lnv_platform.of_PrintDlg (astr_printdlg, lw_parent)
In pfc_n_cst_platformunicode, function of_PrintDlg(), I see:
return pfc_printdlg (ll_hwnd, astr_printdlg)
Then this local external function pfc_PrintDlg() is what uses
PBVM90U.DLL.
Where exactly would I put PrintSetup()? I'm concerned about the two
args that get passed to pfc_PrintDlg() -- I don't think I can just
ignore them, so...?
0 new messages