I've always done my development in a single user OI. Even if we are two in the project team, it's me that do the programming. When I'm finished with a new version of the app, I give a copy to my colleague, who makes the required versions for our clients - multiuser runtime versions and various single user versions. So all the time with OIWG I've upgraded my single developer with the Works upgrades. To make multiuser versions we have all the time used the original 3.0 multiuser runtime engine. This has seemed to work, except now our multiuser OI 3.61 will not run. With OIWG it's really only 3.3 and 3.61 we have used. We skipped the other versions (except we did the upgrades of course, but we didn't do any development work so we didn't make any multiuser versions). So our current OI version being 3.61 might not be relevant. The problem might have occurred any time after 3.3 for all we know.

Now tell us how stupid we have been and what the correct procedure for keeping the multiuser engine up to date is.

- Oystein -

Oystein,

Tell me if I have understood you correctly:

You have an up to date, working copy of OI v3.61 that is single-user (your development system).

Your colleague has a multi-user template into which he puts your applications to distribute them to customers, which does not function due to an unorthodox upgrade process?

Do you not use the RDK to deploy apps, and then just apply bump disks to them as necessary? If that were the case, then your development copy would be the only copy that was pertinent in getting this all to work.

Still a bit confused. Let me know..

BTW, my linux testing has been slowed, because I had to send in my linux machine for service :( (bad keyboard–it's a laptop)

-Scott

Revelation

Scott,

Tell me if I have understood you correctly: You have an up to date, working copy of OI v3.61 that is single-user (your development system).

That's right.

Your colleague …

My colleague takes my copy of OI and simply replaces my 1-user development version of OENGINE.EXE with an n-user runtime version of OENGINE.EXE. In practice we sell 2-, 4- and 6-user systems, so he has one OENGINE.EXE for each of those. His set of multi-user OENGINE.EXEs is version 3.3, from May last year. So they might be too old for the 3.61 system.

We hope you can suggest a solution where we don't have to backup/restore our app back to 3.3 before making multi-user versions from it. I had to do something similar recently (backup/restore to an older version), and it was a lot of hassle. (Backup/restore performed well, but there was a lot of extra stuff that I had to remember to bring along.)

BTW, my linux testing has been slowed, because I had to send in my linux machine for service :( (bad keyboard–it's a laptop)

Well, that can't be helped. I'm happy to hear you haven't shelved it.

(Btw - I think most laptop keyboards are bad, but that's because the layout's different from what I'm used too - especially the numeric pad (I normally use the arrow keys and stuff on the numeric pad). Since I try to use the keyboard rather than the mouse, I have lots of key combinations that become very awkward.)

- Oystein -

View this thread on the Works forum...