Simplicty and flexibility!


Bad DB Version 3.


Started by Peter Birney, PB Associates
Search
You will need to Sign In to be able to add or comment on the forum!

Bad DB Version 3.

I am running a test migration in Version 8.5 of a system currently running under LegEasy4DOS and I am getting this error.

Can anyone point me to why this is happening?


Written by Peter Birney, PB Associates 25/03/21 at 14:09:53 Dataease [{8}]FIVE

Re:Bad DB Version 3.

Does the application migrate or does it end with this message?


Written by DataEase 25/03/21 at 15:55:08 Dataease [{8}]FIVE

Re:Re:Bad DB Version 3.

Download: DEMigrate.log

This is the only message that i receive.  Please see attached log file.


Written by Peter Birney, PB Associates 25/03/21 at 16:07:49 Dataease [{8}]FIVE

Re:Re:Re:Bad DB Version 3.

Here is the RDRR file if it is of any use.


Written by Peter Birney, PB Associates 26/03/21 at 15:43:26 Dataease [{8}]FIVE

Re:Re:Re:Re:Bad DB Version 3.

The problem is that the Application is older than DFD 5.x

You can only migrate from DFD 5.x onwards.

So you need to migrate to DFD 5.x first.


Written by DataEase 26/03/21 at 18:02:08 Dataease [{8}]FIVE

Re:Re:Re:Re:Re:Bad DB Version 3.

Just to be pedantic (Nothing new there!), could you confirm that even though the application has been run using L4D, it is not updated/marked as having been "opened" using anything other that its original DFD Version (I have opened the database in question in DFD4.53, its original version).

I had believed that it would have been updated/marked as a V5.x database, which is why i went straight to use the V8.5 Migration tool.


Written by Peter Birney, PB Associates 27/03/21 at 09:05:53 Dataease [{8}]FIVE

Re:Re:Re:Re:Re:Re:Bad DB Version 3.

L4D is a "people pleaser" Pete so it will run a 4.x app as 4.x and and a 5.x app as 5.x

It wont migrate or do anything to the application if you don't want it to.

The only thig you need to move an application from 4.x to 5.x is to open the session in l4D and switch the version from 4.x to 5.x and run it.


Written by DataEase 27/03/21 at 14:20:53 Dataease [{8}]FIVE

Re:Re:Re:Re:Re:Re:Re:Bad DB Version 3.

The downside of selecting V5 in LE4DOS is that when migrating afterwards the Form layouts and Procedures are apparently lost.

I took the database through DFW550 and thence to the V8.5 migration tool in order to keep them.


Written by Peter Birney, PB Associates 05/04/21 at 09:59:10 Dataease [{8}]FIVE

Re:Re:Re:Re:Re:Re:Re:Re:Bad DB Version 3.

A rock and a hard place at the moment.
The migration of DFD layout to DFW was so poor from the start that it was hardly worth anything...

Which is why they simply removed it in 5.x/6.x (Yes it is confusing that the versions number between DFD and DFW is harmonized but with 1 higher in DFW...) 

Only the people in charge at the moment can answer for the decisions that was made. One would assume that the natural approach to something not working would be to fix it but there is sadly a pattern in DFW that challenges was removed rather being repaired.

When looking in the code one can see that there was work undertaken in 5.x/6.x to allow separate layout on shared DQL's between DFW and DFD but this was abandoned without ever being released. Again why can only be answered by the people present at the time(20 years or more ago).

Our approach to this now is to support legacy products through the LegEasy program, where the focus is to allow users to run old applications rather than focus on migration and conversion.

So if you want to migrate a DFD 4.x application to a modern DFW version you have to either go via DFD 5.x or DFW 5.x and neither route is ideal.


Written by DataEase 06/04/21 at 14:21:02 Dataease [{8}]FIVE
DG3_ForumList