TXA export APP in CW 11.013372 and v12 throws GPF Exception C0000005

[KevinErskine]

I have 15 or so apps and all of the sudden one of them GPFs the IDE when I try and export.

I have tried manually exporting and even using a template with the EXPORT command.

When done in the IDE it GPFs, when done in the template it does nothing

This happens in CW 11.013372 and v12

I can’t really provide the app to anyone since it uses a lot of templates.

I should have stated when I use a template I can export procedure by procedure, but not at the APP level.

Also I have been exporting this app everyday for 15yrs w/o issue as a backup scheme.

Any thoughts?

EXCEPTION-250723-071732.TXT (18.3 KB)

[CarlBarnes]

FORMULA’s are known to crash. In the below Rick had some tips. I would think you could write a UTILITY template to list all FORMULAs.

Sort the APP by module and look at the module/procedure that comes after the last successful one in the exported TXA. Examine that procedure for anything odd. Formulas are notoriously unstable exporting to TXA. I highly recommend getting rid of any Formulas in your APPs.

Another idea. Selectively export one module at a time to figure out which one is causing the crash. Then examine it for oddities.

Clarion crashing when running TXA export

I have an solution consisting of 3 app’s. I recently tried to export one of them to TXA and got the following error Exception occurred at address 6B463189 Exception code C0000005: Access Violation Process PID=4176 Image: C:\Clarion11.1\bin\Clarion.exe Thread 2 Handle=000009DC TID=4796 I looked back through my code backups and found a version that does not have this issue, but that is from 12 releases ago and a lot of changes have been made since. Interestingly all apps still generate co…

Copy Procedure with Formula causes C11 crash, alternate way to copy?

Formulas are very fragile when exporting to txa.

[KevinErskine]

I do not use formulas

[CarlBarnes]

Sometimes an errant few clicks and you add an empty FORMULA.

Do you get a partial TXA?

Figure out the last [PROCEDURE] exported and focus on that one. What changed since export last worked,

Another idea. Selectively export one module at a time to figure out which one is causing the crash. Then examine it for oddities.

[KevinErskine]

OK - THANK YOU EVERYONE!

Until I switched to module view and tried the Export, I was not getting anything, After doing this I was able to see and old procedure which I thought was deleted, but for some reason was not and it was saying it was an external procedure when it was an IDE generated procedure. I deleted it again, exited app, recompiled, then tried the Export and all seems good.

I appreciate all the different views.