Also,
If your going to convert forms and reports, copy the database into another folder, and after converting to 7.1, unload it and load it into the active database.
Bernie Lis
----- Original Message -----
Sent: Tuesday, June 22, 2004 9:23 PM
Subject: [RBG7-L] - Re: RBase 7.5 & 8

My topic at the last conference was
"Don't Convert -- Re-Think It"
I also go from dos 6.5++ to 7.1  re-designing forms and reports and turning many programs into eeps instead.
Take your time, let them run both versions at the same time, as you develop 7.1
keep your new programs in a separate folder and just connect to the dtabase whereever it is.
 
Bernie Lis
 
----- Original Message -----
Sent: Tuesday, June 22, 2004 10:49 AM
Subject: [RBG7-L] - Re: RBase 7.5 & 8

I also have a client where we are running three versions simultaneously. All new development is in 7.x, we have a number of modules in 6.5++ Windows and a large app in 6.5++ DOS that will be converted sooner or later.
 
I personally thank RBTI for allowing this to be done, rather than forcing an "all or nothing" upgrade path.


Emmitt Dove <[EMAIL PROTECTED]> wrote:
Karen,

My recommendation would be to keep running what you are now while you convert.  I understand the reluctance to be maintaining 3 versions, but that somehow seems like the path of lesser difficulty.  Shoe-horning the 6.5++ Windows forms and reports into 7.1 may end up costing more effort than doing an orderly conversion/rewrite.

That's the approach we are taking.  All new work is in 7.1, and as we have time we will convert (more likely rewrite) the 6.5 stuff.  And we do have some 6.5++ DOS running a payroll piece that will probably never be converted.


Now that we're talking about 6.5++ and 7.1 simultaneously,
I have a client on 6.5++ Dos and Windows.  We'd like to convert
the Dos app slowly to 7.1, but we don't want to maintain 3 front
ends, 6.5++ dos (until it's all converted), 6.5++ Windows and
7.1.   

Reply via email to