How to modify a function

[mumfie]

Re: How to modify a function

Am I in the ballpark?

The sample code is a much simplified code of the code we were having the issue with.
The original code creates an sql connection and performs a transactional update of multiple tables by calling additional functions. I did not include these because the simplifed code (without sql access) also exibits same problem.
The code also uses some types defined in another script TChangeRequest. In the original version those are in an external database and are automatically loaded. I have now imported code to a blank database and have found you might have to run the script TChangeRequest for the test code ChanRF_DAO_Test to work.

ChanRF_DAO_Test is a standard test script not a function. Its purpose is to verify that the code works by setting up parameters and calling the functions prior to implemention in web and winform applications. In the simplified code there is only 1 function ChanRF_List_InsertDAO actually being called and it simply outputs the message to trace window

[mumfie]

Re: How to modify a function

Nevertheless, eliminating the parameters of the function, it works just fine after each save.

Thanks. That does help.
I will try to identify what is causing the problem as we likely need the parameters.

[mumfie]

Re: How to modify a function

Nevertheless, eliminating the parameters of the function, it works just fine after each save. I use pointers all the time in parameters, so it is not the parameters either.

have done some further tests and problem seems to be related to
option strict. If we comment it out save works okay.

[csda1]

Re: How to modify a function

Hi Colin,

have done some further tests and problem seems to be related to
option strict. If we comment it out save works okay.

Place the Option Strict within the function near the top, not outside it. See if that works for you. Code outside a global UDF is normally ignored, but may be causing an issue.

[G Gabriel]

Re: How to modify a function

Haven't tested this but might be a factor, though unlikely. When you used option strict, you did dim your variables explicitly, but I wonder if you have to dim the scope as well, i.e.:
dim local OK as L
etc.
You might want to test that as well.

[mumfie]

Re: How to modify a function

Thanks for the responses.
I assumed option strict should be at the top but it looks like it can be anywhere. There is also an option relax to disable checking.
I did assume undeclared variables would be reported at compile time but it appears it is runtime.

e.g. the code below results in runtime error a3="a3 is an undeclared variable". variable not found

option strict
dim a1 as c
a1="a1 is a declared variable"
option relax
a2="a2 is an undeclared variable"
option strict
a3="a3 is an undeclared variable"

[CALocklin]

Re: How to modify a function

Place the Option Strict within the function near the top, not outside it. See if that works for you. Code outside a global UDF is normally ignored, but may be causing an issue.

YES! The Option Strict belongs inside the function. In addition, remove, or comment out, ALL code that comes before the FUNCTION line.

I often put code there to run the function for test purposes during development. However, it has to be remmed out before saving the function if I then want to test it in "real life" from a form, etc. Otherwise, as Ira stated earlier, "you will run the last good compiled version of the code."

As long as there are any lines of code above the FUNCTION line, the program will not see your changes until you close A5 and re-open it. Commenting out the lines is sufficient to solve the problem if, in cases like mine, you might want to just un-rem it later.