Does anybody have any idea what could cause the dreaded:
Quote
EGRIDD~1.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.
...message? Everything was working so good until I tried to get the cell rectangle using %EG_GETCELLRECT then everything went south. Now I can't even get my project to compile. Reinstalled Egrid, rebooted, but still no go.
:twisted:
[TURN ON AGGREVATION]
@#@#$%%^^&&*@$@^**^&#^&, Arrrgh!
[/TURN OFF AGGREVATION]
Quote from: JR Heathcote...message? Everything was working so good until I tried to get the cell rectangle using %EG_GETCELLRECT then everything went south. Now I can't even get my project to compile. Reinstalled Egrid, rebooted, but still no go.
:twisted:
It sounds like a memory corruption error. Not sure why it would happen - there could be 100's of reasons depending on how your code is written.
You mention that you can not compile now. That is strange for sure. Try deleting all of the CODEGEN_*.* files in your code output directory and then do a full re-compile (i.e. press F5). If that doesn't work then email me your project and I will get to the bottom of it.
You are able to load the project into FireFly, right? It is just the compile that is failing?
Check your process/task list (Ctrl+Alt+Del) to see if the EXE is still running in memory when you try to do the compile.
Thanks, I will check the EXE with Task Manager.
Yes, I can load the project into Firefly and perform edits so I don't think this problem has anything to do with Firefly, it is an Egrid problem, or something associated with Egrid.
I'm not at my development PC right now so I will have to wait :( until this evening when I get home.
OK, tried recreating the project as you suggested, but no luck, still get the error message. Also tried a totally new project, plus reinstalling Firefly, but that didn't work either. :cry:
Chris Bristow sent me a new version of SIGRID, couldn't get that to work either, I think you will have to create a new control file for it.
Man I'm really batting 1000 with this stuff...
Does your project work if you omit the code dealing with %EG_GETCELLRECT ???
With regard to SIGrid, can you email me the include file so I can see what functions may have changed their parameters. That way I can update the fireFly control file. The file in question should be named "sigrid.inc".
You're certainly having a fair share of trouble with these grids. :(
Paul,
Quote
Does your project work if you omit the code dealing with %EG_GETCELLRECT ???
No it does not. I commented out the %EG_GETCELLRECT code and it still bombs out. Rebooted twice and the project still bombs. I then created another project using EGRID thinking I created something in my code to originally cause the problem. This new project compiles ok, but when I enter data into the grid and press the Return Key project bombs out. It's almost as if EGRID itself has become corrupted.
I will send you the new SIGRID.inc file.
Quote
You're certainly having a fair share of trouble with these grids.
Tell me about it.
Thanks, I have received your file and I will work on it today.
Here is another tidbit of information. When the project is compiled, FireFly will copy the necessary grid DLL's (SIGrid.dll or EGrid32Pro.dll) to the code output directory (i.e. the directory where the CODEGEN*.* files exist). You are now using new versions of the DLL so I am thinking that maybe FireFly is not overwriting the previous versions that may exist in your code output directory. FireFly should copy the latest version of the DLL's from the CustomControls directory to your code output directory. You may want to try manually deleting the grid DLL's from your code output directory and then re-compile. Please let me know if this works - it is worth a shot.
Paul,
Deleted the .DLL's out of the code output directory and tried to recompile. Out of the four examples I mentioned previously only one of the EGRID demos was able to compile and run correctly. The other three examples bombed out as they always did before.
One thing I did notice about the SIGRID apps is the fact all associated processes do not shut down properly when problems arise, most of the processes are still running and must be shut down manually, EGRID OTOH does a much better job of cleaning up after itself. Might be useful tib-bit of info for someone considering purchasing these two products.
It seems odd that things would remain in memory for both SIGrid and EGrid32. That would indicate that maybe it is FireFly that is the problem. What operating system are you using?
Create a simple sample project that GPF's and email me the entire project. I can then try to trace the problem through the code that you are using and the files that are being loaded and compiled by FireFly.
EGrid and SIGrid are used by many FireFly users so I would think that if GPF's regularly occurred then I would have been warned of it long before now. Incidently, I am able to create programs using both Egrid and SIGrid with no trouble (even using both grids in the same project).
I'm using XP Pro SP2.
Only SIGRID remains in memory, EGrid32 appears to terminate cleanly no orphaned processes that I can detect.
I will zip up a SIGRID and EGRID project tonight and send it to you, but if Murphy is alive and well both projects will run OK on your PC, but not on mine.
I got your projects. I sent you a private email. It is very late here so I only had a chance to take a quick look. I immediately noticed in the EGrid32 project that you are not handling the incoming Window's messages correctly which appear to result in null pointers being assigned and referenced (causing a GPF).
I will check into the projects more in the morning. One thing that you can safely assume is that the grid DLL's do not appear to be the immediate cause of the GPF's you are experiencing.
Guys, maybe im too late, but if i can do something to help, let me know.
:)