same module uncompiled to compiled

same module uncompiled to compiled



Yeah, it doesn't matter if there's something in the l.myvar field- the
file will still be created, just empty (basically).

Scot

<A HREF ="http://www.scotsscripts.com">http://www.scotsscripts.com</A>

Scott Shepard wrote:
> Actually, an add on question...
>
> <MvEXPORT
> FILE="{l.directory $'myvarfile'$'.dat'}"
> FIELDS="l.myvar"
> DELIMITER="">
>
>
> If l.myvar is empty will the file still be created? I haven't
> determined yet if the l.myvar is other than Null yet, but I think the
> file should still created, correct?
>
>
> TIA,
>
> Scott
> IDS
>
>
> Sunday, October 24, 2004, 11:11:57 PM, you wrote:
>
> SS> Hello MvMarkus,
>
> SS> Miva Merchant v4.20
> SS> Miva Engine v4.1000 (Mia VM).
>
> SS> It appears I was in haste. I still have the problem. but not even
> SS> close to what I thought. I am actually using an Mvexport to save some
> SS> data that gets mvimported when update button is pressed. The file is
> SS> not being created however; hense, nothing to import later.
>
> SS> OK! Same question, but using MvExport instead. Everything works great
> SS> in uncompiled version.
>
> SS> again, TIA,
>
> SS> Scott
> SS> IDS
>
> SS> Sunday, October 24, 2004, 6:42:18 PM, you wrote:
>
> M>> Hi Scott,
>
> M>> Without knowing more of the code it's almost impossible to say what actually
> M>> could create this
> M>> problem, but I'd first look at the way how you translated the macros (if you
> M>> had any in your uncompiled script).
>
> M>> Another possible reason could lie in some "minor" changes when form data
> M>> with several variables with the same name is passed on to the processing
> M>> page (using arrays). This change is however older, so that should not be the
> M>> issue.
>
> M>> Which versions of Empresa/Mia are you using?
>
> M>> Markus
>
>
> M>> -----Original Message-----
> M>> From: [email protected] [mailto:[email protected]]
> M>> On Behalf Of Scott Shepard
> M>> Sent: Monday, October 25, 2004 3:38 AM
> M>> To: [email protected]
> M>> Subject: [mrc] same module uncompiled to compiled
>
> M>> Hello merchant-coders,
>
> M>> I'm working on a module that asks for entry data like a password or
> M>> licensing scheme might work. It's in the 'content' function. So, when the
> M>> module is installed, click on the 'TAB' that function executes.
>
> M>> It's working perfectly in versions through 4.13 (uncompiled). When I compile
> M>> and run in either 4.16 or 4.20 compiled Merchant, the entry data function
> M>> isn't processing.
>
> M>> Further, the logic is such that
> M>> the part of the function the asks for the password runs like it doesn't have
> M>> a value. When it works, the code cycles through only once when "Update" is
> M>> pressed. If all the conditions are met, the content function is processed
> M>> fully.
>
> M>> In MM compiled, is there a different way the variable and values of them
> M>> need to be retained in the env so they're still available on the next cycle.
> M>> And yes, these vars are global (g.whatever).
>
> M>> TIA
>
> M>> --
> M>> Best regards,
> M>> Scott
> M>> mailto:[email protected]
>
>
>

Re[3]: same module uncompiled to compiled



Actually, an add on question...

<MvEXPORT
FILE="{l.directory $'myvarfile'$'.dat'}"
FIELDS="l.myvar"
DELIMITER="">


If l.myvar is empty will the file still be created? I haven't
determined yet if the l.myvar is other than Null yet, but I think the
file should still created, correct?


TIA,

Scott
IDS


Sunday, October 24, 2004, 11:11:57 PM, you wrote:

SS> Hello MvMarkus,

SS> Miva Merchant v4.20
SS> Miva Engine v4.1000 (Mia VM).

SS> It appears I was in haste. I still have the problem. but not even
SS> close to what I thought. I am actually using an Mvexport to save some
SS> data that gets mvimported when update button is pressed. The file is
SS> not being created however; hense, nothing to import later.

SS> OK! Same question, but using MvExport instead. Everything works great
SS> in uncompiled version.

SS> again, TIA,

SS> Scott
SS> IDS

SS> Sunday, October 24, 2004, 6:42:18 PM, you wrote:

M>> Hi Scott,

M>> Without knowing more of the code it's almost impossible to say what actually
M>> could create this
M>> problem, but I'd first look at the way how you translated the macros (if you
M>> had any in your uncompiled script).

M>> Another possible reason could lie in some "minor" changes when form data
M>> with several variables with the same name is passed on to the processing
M>> page (using arrays). This change is however older, so that should not be the
M>> issue.

M>> Which versions of Empresa/Mia are you using?

M>> Markus


M>> -----Original Message-----
M>> From: [email protected] [mailto:[email protected]]
M>> On Behalf Of Scott Shepard
M>> Sent: Monday, October 25, 2004 3:38 AM
M>> To: [email protected]
M>> Subject: [mrc] same module uncompiled to compiled

M>> Hello merchant-coders,

M>> I'm working on a module that asks for entry data like a password or
M>> licensing scheme might work. It's in the 'content' function. So, when the
M>> module is installed, click on the 'TAB' that function executes.

M>> It's working perfectly in versions through 4.13 (uncompiled). When I compile
M>> and run in either 4.16 or 4.20 compiled Merchant, the entry data function
M>> isn't processing.

M>> Further, the logic is such that
M>> the part of the function the asks for the password runs like it doesn't have
M>> a value. When it works, the code cycles through only once when "Update" is
M>> pressed. If all the conditions are met, the content function is processed
M>> fully.

M>> In MM compiled, is there a different way the variable and values of them
M>> need to be retained in the env so they're still available on the next cycle.
M>> And yes, these vars are global (g.whatever).

M>> TIA

M>> --
M>> Best regards,
M>> Scott
M>> mailto:[email protected]

Re[2]: same module uncompiled to compiled



Hello MvMarkus,

Miva Merchant v4.20
Miva Engine v4.1000 (Mia VM).

It appears I was in haste. I still have the problem. but not even
close to what I thought. I am actually using an Mvexport to save some
data that gets mvimported when update button is pressed. The file is
not being created however; hense, nothing to import later.

OK! Same question, but using MvExport instead. Everything works great
in uncompiled version.

again, TIA,

Scott
IDS

Sunday, October 24, 2004, 6:42:18 PM, you wrote:

M> Hi Scott,

M> Without knowing more of the code it's almost impossible to say what actually
M> could create this
M> problem, but I'd first look at the way how you translated the macros (if you
M> had any in your uncompiled script).

M> Another possible reason could lie in some "minor" changes when form data
M> with several variables with the same name is passed on to the processing
M> page (using arrays). This change is however older, so that should not be the
M> issue.

M> Which versions of Empresa/Mia are you using?

M> Markus


M> -----Original Message-----
M> From: [email protected] [mailto:[email protected]]
M> On Behalf Of Scott Shepard
M> Sent: Monday, October 25, 2004 3:38 AM
M> To: [email protected]
M> Subject: [mrc] same module uncompiled to compiled

M> Hello merchant-coders,

M> I'm working on a module that asks for entry data like a password or
M> licensing scheme might work. It's in the 'content' function. So, when the
M> module is installed, click on the 'TAB' that function executes.

M> It's working perfectly in versions through 4.13 (uncompiled). When I compile
M> and run in either 4.16 or 4.20 compiled Merchant, the entry data function
M> isn't processing.

M> Further, the logic is such that
M> the part of the function the asks for the password runs like it doesn't have
M> a value. When it works, the code cycles through only once when "Update" is
M> pressed. If all the conditions are met, the content function is processed
M> fully.

M> In MM compiled, is there a different way the variable and values of them
M> need to be retained in the env so they're still available on the next cycle.
M> And yes, these vars are global (g.whatever).

M> TIA

M> --
M> Best regards,
M> Scott
M> mailto:[email protected]

same module uncompiled to compiled



Hi Scott,

Without knowing more of the code it's almost impossible to say what actually
could create this
problem, but I'd first look at the way how you translated the macros (if you
had any in your uncompiled script).

Another possible reason could lie in some "minor" changes when form data
with several variables with the same name is passed on to the processing
page (using arrays). This change is however older, so that should not be the
issue.

Which versions of Empresa/Mia are you using?

Markus


-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Scott Shepard
Sent: Monday, October 25, 2004 3:38 AM
To: [email protected]
Subject: [mrc] same module uncompiled to compiled

Hello merchant-coders,

I'm working on a module that asks for entry data like a password or
licensing scheme might work. It's in the 'content' function. So, when the
module is installed, click on the 'TAB' that function executes.

It's working perfectly in versions through 4.13 (uncompiled). When I compile
and run in either 4.16 or 4.20 compiled Merchant, the entry data function
isn't processing.

Further, the logic is such that
the part of the function the asks for the password runs like it doesn't have
a value. When it works, the code cycles through only once when "Update" is
pressed. If all the conditions are met, the content function is processed
fully.

In MM compiled, is there a different way the variable and values of them
need to be retained in the env so they're still available on the next cycle.
And yes, these vars are global (g.whatever).

TIA

--
Best regards,
Scott
mailto:[email protected]

Hello merchant-coders,

I'm working on a module that asks for entry data like a password or
licensing scheme might work. It's in the 'content' function. So, when
the module is installed, click on the 'TAB' that function executes.

It's working perfectly in versions through 4.13 (uncompiled). When I
compile and run in either 4.16 or 4.20 compiled Merchant, the entry
data function isn't processing.

Further, the logic is such that
the part of the function the asks for the password runs like it
doesn't have a value. When it works, the code cycles through only once when "Update" is
pressed. If all the conditions are met, the content function is
processed fully.

In MM compiled, is there a different way the variable and values of
them need to be retained in the env so they're still available on the next cycle.
And yes, these vars are global (g.whatever).

TIA

--
Best regards,
Scott
mailto:[email protected]