Search:

https://zarez.net/?p=3187

If you mean you are using direct_output then the Writeln just writes what it is given "as-is"

So if you want ANSI in your file use Utf8ToAnsi if you want UTF8 then don't

Note ReadLn in 20.x...

Yes we do sign the exe's

The exe is NOT the problem here it is the DBG file as per the title of this thread

Equally if it is the AV we can't be the only people on the planet using DF and Sophos so why are there not other reports

Up until yesterday it was only one src (our largest) that showed the issue but then another started doing it for a colleague

I don't have the power to remove the AV

Reformatting the output.txt file above and pasting it into HxD shows one has a load of nulls and whilst I don't know enough to read the code it does look corrupt compared to the other in that...

Found this in our code which maybe your issue



// Augmentation from FlexCOM20_Base.pkg to try and resolve bug where vComObject is occasionally 'null' and not 00000
// Attach the DF...

The only one in your list I have used is Chestysoft and that has a 64bit version

What is the actual error you get and which COM method is being called when you get it?

Thanks but that is not the sane error. Yours says the file is missing mine says it is corrupt

No the same Programs folder

So when the complier runs beyond checking for the existence of the exe and dbg file and deleting them does it read either of them in any way ?

The 44k of difference between the two is alot and...

Just tried deleting the exe and renaming the debug, add remove a space and recompile and the only difference to the first time is this

00000010: 8A 92
00000011: B7 88
00000012: 9D 97
00000027:...

15454Not sure if this says much but I ....

Deleted exe and dbg
Compile and run
Runs OK
Copy dbg file
Add a space to source code, remove again and save
Compile and run again
Got the expected...

.

No these ate local folders on all our machines

We use svn but exe and dbg are not in there

the strange thing to me is if I delete them it is fine but if they exist as soon as the compiler has...

Interesting

But I can literally make a tiny change like add a space and re-compile and I get the error when the debugger loads or the studio just drops out

Still no closer to narrowing this down

Deleting the contents of IDESrc has had no effect

Turning off AV has no effect

I get the issue all the time and colleagues using the same codebase get...

If the exe and dbg don't exist at the point of compile it works

If they do then it does not work suggesting it is reading one or both of them and making a decision based on what it sees

Even if...

I could not find anything either

I did find these similar ones complaining about the exe but not the dbg file
https://support.dataaccess.com/Forums/showthread.php?48680-what-does-this-mean...

19.1

All of a sudden several of us are getting this error after the application is compiled

Has anyone else had this error ?

Closing the studio, deleting the exe and dbg and doing it again...

Have you cut 'n' pasted something else in the meantime from a n other application that might explain the rarity

You would need to create a new XML object and use AddElementNS to add the elements reading them from the original, but as Marco says this will need knowledge of namespaces

Also why do you want to...

64 bit cache files have a different name

MyTable.x64.cch

#include is effectively copy and paste the contents of this file here before you compile