Debugger never hits debug point

[aburningflame]

I have a function that looks like this:
OPTION ENCRYPTED_TOKENS
FUNCTION importXLSFile AS P (fileName AS C, batchNo as N)
debug(1)

I use interactive window to call the function
?importXLSFile("filename", 1)

The debug point is never hit, and the application runs as usual. How can i debug this function?

Any help is appreciated. Thanks.

[Steve Workings]

You might try commenting the Option statement out until you have it working, then see if it still works with the Option statement in effect.

[CALocklin]

When creating a function, NEVER put any commands above the FUNCTION line. The only thing that should ever be above the FUNCTION line is comment lines. (Which includes the date/time info Alpha adds and a password line if you use one. You can also add all the comments you want but NOT any code.)

Whenever there is any code above the FUNCTION line, Alpha won't recognize any changes made inside the function until you either rem out the stuff above the line or close the function in the code editor and re-open it. (Or maybe you have to close Alpha and re-open it. It's been so long I don't remember.)

There is one situation where the changes will be recognized - if you click the lightning bolt in the code editor itself. BUT there is a better way....

I used to put code above the FUNCTION line for testing purposes during development. This worked great when I clicked the lightning bolt (or pressed Ctrl-F5) but was a real pain because I kept forgetting to rem it out when testing in the Interactive Window or from a form.

THE SOLUTION
is very simple - put any "test code" below the END FUNCTION line.

Your OPTION Encrypted_Tokens should be the first line of code inside the function. And note that I said the first line of code because it must come after any "Description:" line. You do know about description lines don't you?

Oh, OK, since I can't find it in the Help files anywhere I'm sure most people don't know about description lines so here's the info:

If a description line immediately follows the FUNCTION line in a global function, the description text will be displayed with the autocomplete text. (Although I don't believe it will display until A5 has been shut down and re-started. Again, I'm not sure if it's after the code editor is closed or A5 is closed.) The syntax for the description line is:

FUNCTION myfunction as c (<arguments>)
'Description:<description text>

The description line is a comment line immediately following the FUNCTION line which must start with the word description followed by a colon. (Capitalization of the word description does not matter.) Any text after the colon will be displayed. In other words, it's usually best NOT to put a space after the colon - especially if the description text is long enough to word wrap. Only one line is allowed but if it is longer than one screen, it will word-wrap. (And, fwiw, I've created some that wrapped to 5-6 lines on a 1440x900 screen.)