NetSimple.Open causes Access Violation

[Thys]

Hi,

I'm not sure where in the process of changes on my laptop this started occurring. I have a NetSimple variable on a procedure that is a client object. When it calls the Open method, it throws an Access Violation error. This is fairly new behaviour as it has been working for a long time - only recently did this come up.

Any ideas where to look at?

NetTalk 7.34 (confirmed also on recent versions)
Clarion 9.0
Windows 8.1

Thys

[attachment deleted by admin]

[Thys]

...needless to say that the server and port parameters are populated correctly when the Open method is called.

[Bruce]

have you got the Stringtheory global extension in the app? Are the settings on the Mutl-DLL tab of the StringTheory extension correct?

cheers
Bruce

[Thys]

Hi Bruce.

Yes StringTheory is in the app and the Multi-DLL setting "This is part of a Multi-DLL program" does not compile when switched on.

Thanks

[Bruce]

if this is part of a multi-app suite ( a "Multi dll" program") then add stringtheory to the data dll, and set multi-dll settings in both apps appropriately.

[Thys]

Hi Bruce.

No, there is only one app in the solution. And the only 3rd party templates are NetTalk and StringTheory. I'm also using the Version Resource template.

Thanks

[Thys]

Here is the GPF Reporter information again - this time the EXE was properly compiled in debug mode.

[attachment deleted by admin]

[Bruce]

Is the call to .Open perhaps before the call to .Init?

Also make sure the correct version of the NetTalk DLL is in the application folder.

[Thys]

Hi Bruce.

No, I wish it was before Init - then it would all make sense.

I copied the NetTalk DLL from the "C:\Program Files (x86)\SoftVelocity\Clarion9\accessory\bin" folder myself, although the project is set up to do it automatically. On the file's details tab it does have 7.34 as the product version although I see in the GPF Reporter's text that it is said to be a build for "Clarion 9 beta". I also checked for duplicate versions of this file elsewhere and could not find any.

Thanks

[Bruce]

I'm out of ideas. Is it only happening to this window in the app? If so then I guess try and determine what makes this window different to the rest. What I usually do is try and duplicate the effect in a separate example - and if that works ok then I compare the 2 procedures. If it fails then you have an example to send me for testing here.

cheers
Bruce

[Thys]

OK, I will try some of that.

Thanks

[Thys]

Bruce,

I managed to fix the problem, thanks for you time. Here's what happened.

The following items did not fix the problem:

• Uninstalled NetTalk, cleaned everything and install again
• Move code to another procedure

I did manage to get it working is a small new app, so it showed that the NetTalk installation does work. So as a last resort (before reinstalling Clarion...) I exported the APP to text and imported into a new APP. That solved it. It does indicate that some inconsistency in Clarion had caused this.

Thys