The update didn't appear to upgrade my OENGINE.RUN. After I renamed OENGINE.RUN to OENGINE.EXE and re-ran the update it showed the correct version. Shouldn't this occur with one step?

Thanks,

dbakke@srpcs.com

SRP Computer Solutions

I would think that it should but, it appears that you are right. Allow me to look into it further and I'll let you know what I find out.

Thanks,

Tom Dunlop

Revelation Software

Hi Don:

I've replicated the situation here. It will be brought to the developers' attention sometime mid-week. I'll let you know the outcome here.

Thanks,

Tom Dunlop

Revelation Software

Don,

My understanding is as follows:

When we shipped the 3.72 pre-release, we disabled the copying of the updated Runtime engine. We did this because it is not a final 3.72, and we don't want people to deploy on beta software. When the final version of 3.72 is released everything will be done in one step.

If you have a critical customer situation here (they really need 3.72 asap, let me know and I will assist.)

Kurt

Hi Kurt,

Thanks for the written and verbal update.

No, we do not have an urgent customer problem. If we did, we would just make sure their runtime engine was named OENGINE.EXE and go from there.

Cheers,

dbakke@srpcs.com

SRP Computer Solutions

View this thread on the Works forum...