Hi All,
Let say in my OE10.2B products, I am using OE Studio (32-bit) to compile my source on OE RDBMS (64-bit). Am I right to say that the produced r-code is still in 32-bit (sorry for my noob-ness here)?
Currently these setup is throwing me error below when I am using the 32-bit Client to run the application:
Invalid version, 1005 (expected 17391) in object file <filename.r>. (2888)
From PKB Article No. 11246 stated:
As of 10.1A onward, you cannot run code compiled with Progress 32-BIT on Progress 64-BIT or vice-versa.
Is the article scenario the same as mine? I assume the mentioned Progress (32-bit) is referring to OE Studio or similar, and Progress (64-bit) is referring to RDBMS?
Thank you.
You should really look to upgrade to 11.x as the rcode is bitness agnostic again in 11.x, plus it's a much more modern release with support that will last a lot longer then 10.x :)
You should really look to upgrade to 11.x as the rcode is bitness agnostic again in 11.x, plus it's a much more modern release with support that will last a lot longer then 10.x :)
Though I have tested with compilation with OE Studio (32-bit) on OE RDBMS (32-bit), and running the 32-bit Client is working, I just want to clarify by my previous post.
> Let say in my OE10.2B products, I am using OE Studio (32-bit) to compile my source on OE RDBMS (64-bit).
The bitness of the DB does not matter (assuming you mean that you have the db connected from the client in order to compile). What matters is what client (32 or 64-bit) is going to run that compiled r-code. It has to match (for 10.2B). Eg 32-bit r-code can be run on 32-bit client, ditto for 64-bit.