Thanks! I have seen some chatter about such an animal and will plug it in.
So, there shouldn't be any problem with the DRIVER=winspool line when
printing on a Novell network?
-----Original Message-----
From: profox-bounces .AT. leafe DO.T com [mailto:profox-bounces@leafe.com] On Behalf
Of Michael J. Babcock
Sent: Friday, April 30, 2004 10:26 AM
To: profox .AT. leafe DO.T com
Subject: Re: VFP6: Syntax Error
Crooks, David L. wrote:
> The app is distributed already. I think it might be a Tag issue in
> the report which is included in the EXE. So, I might have to resend
> an EXE and will then check the debug info.
> Thanks!
If you go that route (with rebuilding), you might look at using a Project
Hook class that automatically goes through your reports and clears the
report info. Here's my BeforeBuild code in my project hook:
LPARAMETERS cOutputName, nBuildAction, lRebuildAll, lShowErrors,
lBuildNewGuids
FOR EACH oFile IN Application.ActiveProject.Files
WITH oFile
DO CASE && Check .Type to see what operation
needed
CASE .Type = "R" && clear out report
tags
lcCopyFile =
LEFT(.Name,LEN(.Name)-1) + "*" && will make it ??* to get all parts
USE
(LEFT(lcCopyFile,LEN(lcCopyFile)-1)+"x")
&& mjb 01-18-01 thanks to
wOOdy from Profox
LOCATE FOR objtype=1 AND
objcode=53
IF FOUND() THEN
replace Tag WITH "",
Tag2 WITH ""
IF "ORIENTATION=1" $
Expr
REPLACE Expr
WITH "ORIENTATION=1"
ELSE
REPLACE Expr
WITH ""
ENDIF
ENDIF
USE && close report file
ENDCASE && .Type
ENDWITH && oFile
ENDFOR
As you can see, I took this from a wOOdy tip back in 2001!
--
Michael J. Babcock, MCP
President/CSA, MB Software Solutions, LLC http://mbsoftwaresolutions.com
"Bettering your bottom line by helping you work smarter, not harder, with
custom software solutions."
©2004 Crooks, David L. |
