Subject: | Re: Delivering Question
| Date: | Fri, 3 May 2019 08:57:09 -0400
| From: | "Steven Green" <greens@diamondsg.com>
| Newsgroups: | pnews.paradox-development
|
your note says you put the ldl there, but it needs the lsl to compile the
form
--
Steven Green
Myrtle Beach, South Carolina, USA
http://www.OasisTradingPost.com
Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Peter" wrote in message news:5ccba438$1@pnews.thedbcommunity.com...
my system:
frm.fsl | lib.lsl
compiler warnings = True
compile with debug = True
everything works fine
frm.fsl | lib.lsl
compile warnings = False
compile with debug = FALSE
save/deliver
frm.fdl | lib.ldl
everything works fine
Customer System
frm.fdl | lib.ldl
getting some unexpected results (UAC blocking cmd.exe I think)
need to troubleshoot so added my dev copy frm.fsl
now
frm.fsl | lib.ldl
This is the problem
frm.fsl put into design mode to setup some traps
push [F9] (syntax check)
error "cannot find file"
USES: :dir:lib.lsl
I think the problem has to do with the "compile warnings" setting
Peter
On 04/29/2019 05:40 AM, Mark Bannister wrote:
> What's the error?
>
> On 4/26/2019 7:27 PM, Peter wrote:
>> Is there any order in delivering forms, libraries etc?
>>
>> I delivered a new version of a form that works perfectly on my test
>> system but when I install it on my customers system it will not work.
>>
>> I then installed the undelivered version of the form and it balks at the
>> libraries listed in the USES section. The libraries are delivered and
>> have the exact same date/time stamp, as are on my test sytem. Thanks for
>> any help.
>>
>> Peter
>
|