Hello!

Here one of those strange errors of OI. When I compile large programs in my laptop (XP professional) the system editor results viewer returns: Compilation was successful!; but when i close and open again the program there are no changes (this is really irritating!!), then if i try this in other laptop (same model, and operative sysytem) compiles well.

Is really important for me to resolve this matter cos I work with my laptop, and i can´t be using others machines for doing my job.

What can I Do??????????

Does the object code change and the source code remain unchanged?

What network driver?

The Sprezzatura Group

World Leaders in all things RevSoft

I too have many very large programs.

I have found that the best solution, is to find chunks of code that can easily be taken out into callable subroutines, so that the code is smaller, and the compiled code is also smaller.

Even on OI32, the size of the compiled code has the same limit as OI16.

Call the subroutine, and pass any variables back and forwards.

If you have a COMMON then this is even easier.

Another alternative, if your source is large, but your object code is not reaching the limit is to use $INSERT.

Put some of your debugged subroutines into an INSERT and add the $INSERT at the end of your code.

The source will then be much smaller and will save.

The reason you should only do this with perfect debugged code, is that the debugger will stop at the $INSERT line and not show you through the code.

Colin

the object code not change and the source code remain unchanged. Any change at all.

What network driver? All network driver v1.5

Thanks Colin, that can be a good solution with new programs, but if i have to make a change to any other large program even a (simple line) that was programed by another programer, i will have to segment it all, and it´s against our programing standar, and represents double work. But if there is not other way to solution it…

Thanks again. Alejandro

We vaguely recall similar problems on some 16 bit versions of OI. We used to keep a few thousand "**" at the end of the code and remove some of these and sometimes that would make a difference. We don't recall seeing the problem since going 32 bit but that is no guarantee. The obvious point is that there will be no fixes as 16 bit OI is no longer supported.

A trick we frequently use to ensure the latest object is on the stack is to run RTP27 "PROGRAMNAME" from the execute line though whether this will have any effect obviously would need to be tested.

The Sprezzatura Group

World Leaders in all things RevSoft

thank you, Sprezzatura Group. I will try that. I migrate a test version of our product to oi32 v4.1.3 and the large programs compiles well, but when i try to use the client server workspace (of my application) present a message box that says: "The language in the environment (INTERNATIONAL) is not one of the supported languages!" What can i do to correct that??

thanks again for your time and help

Alejandro

Alejandro-

If you are developing in OpenInsight you are supposed to be a Works subscriber.

Please check your email.

Thanks-

Ok i will check it. thanks.

View this thread on the forum...