I would really like to upgrade to OI 7, but I have a number of clients who, for various reasons, will be remaining at version 4.0.3 for the next next year or so. Will I still be able to support these clients (ie: deploy changes to their applications) if I upgrade? Is it possible to have 2 versions of OI running on the same computer? I suppose there is a licensing issue there .

Thanks,

Gray Cunningham

Gray,

I won't comment on the licensing issue other than to say that I believe Revelation is realistic about the need to support multiple versions of OI. We too have clients who can't migrate from 3.7.x yet.

You can develop in OI 7.0 and deploy into 4.0.x with these caveats:

- Don't use OI 4.1.x/7.0 specific features like OLE controls, Slider bars, etc.

- Forms compiled in 7.0 use extended styles for improved visual appeal. However, the drawback is when these forms are brought into a non-7.0 system they tend to look a bit off. The reverse problem also occurs when moving forms from 4.x or earlier into 7.0. However, there is a free utility (from our website) that will update all your forms to look correct in 7.0.

- Even though OI 32-bit can handle records and variables ]64K, some of the tools were unable to manage entities that were that big. These have been improved throughout 4.1.x and 7.0 so just keep that in mind.

You can run multiple copies of OI on one machine. However, non-7.0 versions cannot run multiple copies of Form Designer and System Editor. So it might not help you unless you use one copy for development and another for runtime testing. 7.0, however, is very nice because you can run complete sets of tools for each instance of OI you are running.

[email protected]

SRP Computer Solutions, Inc.

Don,

Thanks for your quick response. I look forward to speaking with you in person in New Orleans at the Vendor Fair and I will also be attending your "Professional GUI" presentation.

Thanks again,

Gray

Gray,

You are most welcome. I look forward to meeting you in New Orleans as well.

[email protected]

SRP Computer Solutions, Inc.

Don (or anyone else),

I am ready to upgrade my OI 4.0.3 and I want to be sure of the sequence of events that I need to perform. As I see it, I have to first upgrade to 4.1.3a, then to 7.0 and then to 7.0.1…is that correct?

I was wondering if there is an easier and cleaner way using the OI 7.0 that came on the Works CD, upgrading to 7.0.1 and moving my apps (some inherit from others) via AppBack (or something else).

Thanks,

Gray Cunningham

Gray,

I tend to upgrade from 4.0.3 in the following manner:

4.0.3 to 4.1 (4.1 was a major release - I like to hit all the major releases)

4.1 to 4.1.3a

4.1.3a to 7.0

7.0 to 7.0.1

If install 7.0 from the WORKS CD you can then upgrade to 7.0.1. The only pitfall, that I am aware of, in installing dire directly from the CD is that 7.0 does not have the REPORTER.EXE. The REPORTER is no longer supported, however it will run. If you have reports that were built in the REPORTER then you will need to take the upgrade path.

Sean

I am tempted to install from a "clean" OI 7.0 and upgrade to 7.0.1, since I don't use Reporter…is AppBackup my best bet for the actual transfer of my apps? Will I have to run any kind of conversion routines (or do anything to my forms, etc) that the OI 7.0 upgrade would have done had I gone that route instead? Don mentioned that SRP has a free utility that tweaks the appearance of forms that were created in 4.x so that they look better in 7.x, which I will have a look at.

Thanks,

Gray

I've recently upgraded development copy to OI 7.0 and just downloaded 7.0.1.

It looked nice to start again from clean Works copy of OI 7.0 - but what about transferring all those standard screens, routines, etc. I'd added in SYSPROG?

Hence I did a hybrid. After backup, I upgraded my dev OI 4.1.3 to OI 7.0. I also did a separate clean 7.0 install from Works CD. Then a simple program to find all those DLLs, OCXs, etc. in the upgraded copy and not in the clean one (and there are lots!) - and delete them. Then test to make sure it all works - which it has (though I could have copied back any which shouldn't have gone).

Then I've used same process on copies of client systems, including the tidy-up. The reload clients on site (transplanting their site data vols).

Only problem has been some initial erratic behaviour on client workstations which RTI assure me is a Windows self-registration problem cured in 7.0.1 - which presumably would still happen if one upgraded on site instead of reload.

Richard,

That is why I do all that in an account below SYSPROG - call it say TOOLS. Then have MyApp inherit TOOLS. Thus for a transfer to other system I just have to do an Appbackup of TOOLS. Of course you could try an RDK Upgrade/module extract on SYSPROG and grab all you want.

View this thread on the Works forum...