---- Wed Jan 24 13:46:28 2018 ----UTALTSEDDLER:- procedure running :

---- Wed Jan 24 13:46:28 2018 ----BESKJED1:- procedure running :

---- Wed Jan 24 13:46:31 2018 ----OVARBEIDE:- procedure running :

---- Wed Jan 24 13:46:31 2018 ----OVTOPP:- procedure running :

#1: MultiView error: Unknown field HYDE

#2: MultiView error: Unknown field HYDE

#3: MultiView error: Unknown field HYDE

#4: MultiView error: Unknown field HYDE

#5: MultiView error: Unknown field HYDE

#6: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:31 2018 ----OVLAMEL:- procedure running :

#7: MultiView error: Unknown field HYDE

#8: MultiView error: Unknown field HYDE

#9: MultiView error: Unknown field HYDE

#10: MultiView error: Unknown field HYDE

#11: MultiView error: Unknown field HYDE

#12: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:31 2018 ---- Returning to OVTOPP :

---- Wed Jan 24 13:46:31 2018 ----OVOPPHENG:- procedure running :

#13: MultiView error: Unknown field HYDE

#14: MultiView error: Unknown field HYDE

#15: MultiView error: Unknown field HYDE

#16: MultiView error: Unknown field HYDE

#17: MultiView error: Unknown field HYDE

#18: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:31 2018 ---- Returning to OVTOPP :

---- Wed Jan 24 13:46:31 2018 ----OVPAKKING:- procedure running :

#19: MultiView error: Unknown field HYDE

#20: MultiView error: Unknown field HYDE

#21: MultiView error: Unknown field HYDE

#22: MultiView error: Unknown field HYDE

#23: MultiView error: Unknown field HYDE

#24: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:31 2018 ---- Returning to OVTOPP :

---- Wed Jan 24 13:46:32 2018 ---- Returning to OVARBEIDE :

---- Wed Jan 24 13:46:32 2018 ----UTARBEIDE:- procedure running :

---- Wed Jan 24 13:46:32 2018 ----UTTOPP:- procedure running :

#25: MultiView error: Unknown field HYDE

#26: MultiView error: Unknown field HYDE

#27: MultiView error: Unknown field HYDE

#28: MultiView error: Unknown field HYDE

#29: MultiView error: Unknown field HYDE

#30: MultiView error: Unknown field HYDE

#31: MultiView error: Unknown field HYDE

#32: MultiView error: Unknown field HYDE

#33: MultiView error: Unknown field HYDE

#34: MultiView error: Unknown field HYDE

#35: MultiView error: Unknown field HYDE

#36: MultiView error: Unknown field HYDE

#37: Error 402 Getting Field Data.

Unknown field.

---- Wed Jan 24 13:46:33 2018 ---- Returning to UTARBEIDE :

---- Wed Jan 24 13:46:33 2018 ----UTLAMEL:- procedure running :

#38: MultiView error: Unknown field HYDE

#39: MultiView error: Unknown field HYDE

#40: MultiView error: Unknown field HYDE

#41: MultiView error: Unknown field HYDE

#42: MultiView error: Unknown field HYDE

#43: MultiView error: Unknown field HYDE

#44: MultiView error: Unknown field HYDE

#45: MultiView error: Unknown field HYDE

#46: MultiView error: Unknown field HYDE

#47: MultiView error: Unknown field HYDE

#48: MultiView error: Unknown field HYDE

#49: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:33 2018 ---- Returning to UTARBEIDE :

---- Wed Jan 24 13:46:33 2018 ----UTOPPHENG:- procedure running :

#50: MultiView error: Unknown field HYDE

#51: MultiView error: Unknown field HYDE

#52: MultiView error: Unknown field HYDE

#53: MultiView error: Unknown field HYDE

#54: MultiView error: Unknown field HYDE

#55: MultiView error: Unknown field HYDE

#56: MultiView error: Unknown field HYDE

#57: MultiView error: Unknown field HYDE

#58: MultiView error: Unknown field HYDE

#59: MultiView error: Unknown field HYDE

#60: MultiView error: Unknown field HYDE

#61: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:34 2018 ---- Returning to UTARBEIDE :

---- Wed Jan 24 13:46:34 2018 ----UTPAKKING:- procedure running :

#62: MultiView error: Unknown field HYDE

#63: MultiView error: Unknown field HYDE

#64: MultiView error: Unknown field HYDE

#65: MultiView error: Unknown field HYDE

#66: MultiView error: Unknown field HYDE

#67: MultiView error: Unknown field HYDE

#68: MultiView error: Unknown field HYDE

#69: MultiView error: Unknown field HYDE

#70: MultiView error: Unknown field HYDE

#71: MultiView error: Unknown field HYDE

#72: MultiView error: Unknown field HYDE

#73: MultiView error: Unknown field HYDE

---- Wed Jan 24 13:46:35 2018 ---- Returning to UTARBEIDE :

---- Wed Jan 24 13:46:35 2018 ---- Returning to OVARBEIDE :

---- Wed Jan 24 13:46:35 2018 ---- Returning to BESKJED1 :

---- Wed Jan 24 13:46:35 2018 ---- Returning to UTALTSEDDLER :

---- Wed Jan 24 13:46:35 2018 ---------------------------------------

Hi.

What version did you migrate from?

This is character set problems.

in 2015 we migrated from v5 to 7 and then to 8 and now 8.5

we have also 3 more letters in the alfabet ÆØÅ 

looks like after update  the letter Ø dont work any more.

There should be no such problem moving from 8.0 to 8.5 as there is no migration of forms/tables etc. The only migration is versioning of files.

However there can be this kind of problem if you move from pre 7.x up to 7.x and beyond.

The problem is due to ASCII characters used pre 7.x

When migrating to 8.5 there should be a backup copy made automatically in a sub directory under your App Catalogue.

If you are sure this app came from 8.x and this problem occoured when you migrated to 8.5, please zip the 8.x version down and send it to us so we can look at this problem.

I wil send you the migrated one and inside wil also be the backup one

One thing you can try is to copy the ZTERMDEF.DBZ and DEMESSAG.DAT from the DataEase 8 that works to DataEase 8.5

These files are the ones involved with national characters and they have previously been doctored for Norwegian by West Soft AS.

if this works, just write protect them in DataEase 8.5 so they don't get overwritten by future updates.

cant find the files anywhere

Found the files but didnt work

its just one word that is making all this probloms for me. i have tried to chainge it from Høyde to Hoyde but i cant get it to work. can you guys help me?

No. Didn't think it would as this is a problem between 5.x/6.x and 7.x onwards.

The problem is that pre 7.x DataEase used ASCII for data and ANSI for GUI. This is not a problem in Windows but a big problem for Norwegian/German etc. as the national characters is in widely different position in ANSI and ASCII.

The different national distributors had made DEMESSAG.DAT AND ZTERMDEF.DBZ to fix this in 5.x/6.x and when migrating to 7.x onwards one needed to use a similar DEMIGRATE file so it was all migrated correctly.

If this was fixed when migrated to 7.x/8.x the problem should never again arise.

This is why we are a little surprised that this problem only occurred when you moved from 8.x to 8.5 and need to see the original app so we can figure out why.

The problem is "double" when it happens so the solution is to:

change the name in the table.

Edit the offending Derivations and re-insert the field in reports etc. as it will be wrong everywhere but in a non-matching way ;-)

what do you need from me to find this out?

We need a zipped version of the orginal 8.x application before migrating to 8.5.

you can upload it here as a hidden upload i.e. choose "Do you want this file to be available for all users? NO".

Please add a high/high user to the app before zipping it.

i was mistaken we used the 8.5 (beta)

Hi again.

This app is the the current one with the problem. 

We are working on the assumption that this problem occurred when you migrated to the latest version of 8.5 so we need the last version of your app where you didn't have the problem so we can see why this has happened now.

We can see from the DEMigrate.txt from 11.03.15 that you had a lot of these problems when you originally migrated to DataEase 8.

What we can't understand is how they were fixed then and have now returned?

These are the problems we would expect to see when migrating from DFW 5.x/6.x Non-english to DFW 7.x onwards english.

This is the last working program we used.. the backup files that was not migrated to the new is in the zip file i sendt to you.

but now i cant chainge the login

soo the login is user: trygve password: anne

Thanks ;-)

What version of DataEase 8 did you use and could you list forms/reports that has the problem.
All the best.

we used the 8.5 beta.. and that woked but we move the company.. and i couldnt chainge the adress but whit the new 8.5 i could. but then i had probloms whit the Ø what i can find out is that the broblom start at the ORDRELINJER but im not shure. the one that program this isnt here any more so i dont know.

have you figured any thing out?

This is a mystery.

Opened it here in the attached 8.5 beta and it worked, then I migrated it to 8.5 Final and it worked.

What version of 8.5 is it you are trying to use?

If you follow the steps here you wil see the problom.. when we do this i get the error. and its has every thing on the pages but missing the HØYDE on every page when we print it out..

Hi.
Finally got to the bottom of it.

The problem is history and character sets as predicted.

There is an old mechanism for converting ASCII to ANSI which use the file convert.mig.

All the information here is that this file should only be necessary when migrating the app, but it seems that that is not 100% true.

The problem is that in your old DE85 you have been using the norwegian version of this file called Norwegian.mig.

There is no way of setting which file to use as it will automatically use convert.mig so the solution is to copy the file norwegian.mig over convert.mig.

If you do this in your 8.5 installation and then write protect it so it won't get overwritten by any future updates to 8.5

It worked thank you soo mutch :)