Strange Run Time Problem

Started by Marty Francom, July 11, 2005, 02:22:08 PM

Previous topic - Next topic

Marty Francom

I have been collaberating with another programmer in build a FireFly program.  The problem is that when I compile the program (from the same source file)  It compiles fine.  But when trying to run the program I get a  Windows Error Message:

"Rx32W  Main StartUp program has encountered a problem and needs to close. We are sorry for the inconvenience."    

We have check file versions of the WIN32API and other INC files and other include files, no luck.  I have set up a second computer so my file directories are the the same as my fiends.  But still same problem.  

When he compiles the program and sends it to me,  it will run just fine.

He uses  Windows XP Pro   I am using Windows XP Home.

I think their might be a problem with the project file.  Is here a way I can delete the project file then recreate the project addind the forms that have already being created allong with the include files?  If so, how I rebuild a project from the only the form files and the INC file?

Any help will be greatly appreciated.
...Marty

TechSupport

hmmm.... that doesn't sound like a problem would be attributed to the project file. The project file is only a simple text file. You can open it in any text editor for yourself.

Are you 100% sure that your EXE is getting created? I mean, does the date/time stamp on it change after you compile. I am thinking that maybe Windows is not creating the EXE and you are running an old version of your EXE.

Do you use a source code versioning system - one that may be setting read only attributes to your source code files?

Are you outputting the generated source to a separate directory? If yes, then you may want to try deleting all the files in it and then re-compiling your project.

Try loading the resulting CODEGEN_*.bas file into the PB Editor and compile it from there. Also, load the CODEGEN_*.rc resource file and recompile it from inside the PB Editor. Do you get any errors?

Mark Strickland

Paul,

I am working with Marty on this project.  I can compile it on two different machines I have (both XP Pro) and it works fine.  I zipped up the complete project file structure and sent it to Marty and the EXE compiled by his machine will not run on his machine or mine.  We are not using any tool for source version control.

The program "dies" on launch.  You never see the first window.  The program uses some Cheetah DB's and I even took his DB's (thinking they might be corrupted) and my EXE but it all works fine on my machine.

The only time I have had a problem like this is when an array is not DIMed properly and you go beyond the upper bounds of the array.

We did verify all of the INC file versions (commctrl, win32api, etc).  The EXE file is EXACTLY the same number of bytes compiled on his machine and on mine.

Deleting all of the generated code and EXE before compiling is a good place to start.

Thanks for the help.

James Klutho

You might try opening up the **main.bas file in the PB editor and compiling from there.  Something might show up.  I like to separately compile generated code and read it as I go along.  If you are having Firefly generate tons of toolbars, menus, tab controls, OCX etc in a big complex app maybe something is getting confused.  Throwing into the Pbedit debugger is also an option.

James Klutho

Also you might check to see if there is a problem with the resource compiler.  I seem to remember a bad one was released sometime back.  Just a thought.

Marty Francom

I had success compiling the project.  What finally fixed the problem was this:

1) Load the project into Firefly
2) Clicked on the explorer tab of FireFly's Workspace Dialog Box
3) Click on every form and module
4) made a minor change and re-saved the form or module
5) Save the Project
6) Compiled Project
7) Ran the compiled program successfully. !!!!

Apprently the project file was not loading all the forms & modules.  It's surprising to me it still compiled.  Oh well,  as long as it's working that's the main thing.