Hey all:

Is there any way to keep Debugs in your scripts but comment them or render them deactivated until you need them? I am trying to meticulously debug and, once a script is working, I HATE the idea of having to delete 40 debugs I may need later if a simple change is made to the script.

And is there any way (plugin, maybe?) to place line numbers in a FM script?

TRhe lack of these two features (or my lack of knowing how to implement them) is killing me.

Thanks

Kurt

The best thing, if you can spend the money, is to buy Developer. It has a Debug Scripts mode, which does everything you would want and more. It steps through scripts one step at a time, or to your set break points, etc.. And you don't have to remove anything, you just turn the mode off, back to normal, when you've got it working.

But, another cheap trick I use is:

If [ 1=0]

do stuff

End If

Obviously this won't run, and alway obvious how to turn it back on. Kind of ugly though if you do it a lot.

It can be incorporated into an existing If [] step:

If [ Something = something else and 1=0 ]

do stuff

End If

or, the contrary, always true:

If [ something = something else or 1=1 ]

do stuff

End If

(P.S. You may want to put () around your earlier arguments, to keep them separate.)

I second Fenton. Get Developer--it's worth the extra money for the Script Debugger, for the Database Design Report, for the capability to develop custom functions, and for the ability to create stand-alone runtime programs!

Thanks gents.

I had been considering developer a while back. Is it true that the executable that are generated are really, really large? I had heard this was an issue with Developer.

Thanks

Sorry for the slow reply. Been nasty sick.

Kurt

The runtime solution can take up to 40 MB of disk space because the FileMaker "engine" is included. But you can run your solution without the added runtime files if you have the regular FileMaker Pro files installed on the computer at issue.

Thanks for the data.

Kurt

When I coni