The following has been compiled from various responses to questions in the clarion newsgroups. Authors have been mentioned where possible.
Occasionally while using clarion you may get a runtime error mentioning WSLDIAL. Hopefully some of the information below will help you to track down the reason.
Sounds like use a memofield without open the file
You have a control or controls in the window/report you trying to open that has no the Use variable specified. Most probable is that you've erroneously used ? in front of variable name as a value of the USE attribute, e.g.
This occurs when the threaded variable manager tries to swap in a threaded variable for which it has no saved value. It should never happen, and I don't know of any circumstance in which it does happen. If anyone has a reproducible instance of it (preferably small) I'd like to see it.
Richard Chapman TopSpeed Corporation
Carefully delete all compiler debris files, then recompile all code and components using the same Run Time Library property.
To summarise : There is a bug in the intellimouse driver when running lots of programs under Winnt that (in theory) has been fixed with version 2.2a (document Q189770 at microsoft support) The workaround is to go to the list of apps that intellimouse should ignore and add Clarion to them.
This error occurs when trying to run an application and opening a window that has no resources allocated or defined. This usually occurs when a procedure is called from linked in library.
To remedy this problem, go into the project properties (Project button from the Application tree window) and insert the *.rsc file associated with the module returning the error. *.rsc files are usually generated in the \obj subdirectory of your installed CW and there is one for each generated …clw.
Place the file in the project tree in the section named "Library and Object files". FAQ from Steve Parker, http://www.par2.com
WSLDIAL 02 means that the RTL can't find a WINDOW/REPORT resource requested from the OPEN statement. Usually this is because missed or broken RSC file at link time.
Alexey Soloyjev, 3June99, topspeed.products.c5pe
I have fixed the WSLDIAL Internal error 03 problem (Incorrect use variable)
Error 513 - internal error 13
Error 516 seems to be the same problem
Check the c:\cwee\bin\c5ee.ini file for the entry below:
Make sure that it (and any other path related stuff) points to the correct drive/path.
Check the size of Clarion5\Bin\C5Brw.INI. It's probably near or over 64Kb. If so, load it in a text editor and remove the sections for files you don't need.
Delete the C5brw.ini file in Clarion5/bin directory, it most likely points to wrong (non existing) directories somewhere or has grown >64K
Best regards, Arnor Baldvinsson [Team Topspeed - Internet Connect]
(Note: This was not in the original post by Kevin B. Erskine. It is a compilation of several responses)
This error is generated by incorrect data definitions. Declarations must be the same throughout apps and dlls eg: SampleQ Queue,THREAD,external,dll SampleQ Queue,THREAD,dll (Missing the external attribute)
2 other known Causes.
- Naming a program DLL same as Windows one, ie SECURITY.DLL - http://blogs.msdn.com/oldnewthing/archive/2004/07/02/171769.aspx
- When declaring data in multi-dll , It appears that Clarion 6 needs the THREAD attribute in addition to the EXTERNAL, whereas previously Clarion 5/55 did not require it.
It's an internal library error that has to do with an internal mouse hook. Since that hook is used for flat buttons, if you toolbar happens to have flat buttons, dont make them flat. As far as I know this was fixed in the last c5b release or at least I have not seen it recently.
Parameter Typing Error - GPF?
This indicates an internal error in the handling of ANY variables - if you can email me an example APP/DCT I will investigate.
Richard Chapman TopSpeed Development Centre