Troubleshooting

Top Previous Next

If the template seems to misbehave and don't do what this manual shows, do the following:

Test the template with the “autolog” program provided with the examples of Clarion 5.5 or with the “school” program of Clarion 6. The template is well tested with those programs.

Also, try the supplied example. This example is developed in Clarion 5.5 and you may open it with Clarion 6.x as well (backup it if you plan to open it with Clarion 5.5 later).

Two things may happen:

1)	If the example works ok, then there is “something” in your app that is incompatible with our template... May be another 3rd party template? Please carefully review the previous section, “Template considerations”. If the problem persists, contact me for further assistance.

2)	If the example doesn't work...

Assuming that the example program works and yours don't, do the following. Disable the code generation with the “Disable the whole template” option in the “All” tab. Test your program and it should work ok, like if the template is not installed (It has to be that way, as no code is generated). If your program still has problems, solve them before continue (as they are not related with this template).

Done and verified that, activate the options one by one, testing the program on each one. May be the problem is on an unexpected section of the template. When you narrow down the problem, contact me for further assistance.

If the problem happens when you activate the “Buttons” tab, then you may check the “debug” option, which will generate in the same directory of your program a file called JALDEBUG.INI containing useful information (for me) about the template activity. You can send this file to me. In case that this information were not enough, you may receive a modified version of the template so you can generate an extended version of the debug file for us to find what your problem is.