I'm about to start upgrading to V7 Dev. Has anyone imported data from runtimes made with 5.5 or 6 into V7? I assume that if I use the same binding key and master password it should work, but has anyone done it?

Also, I have loads of phone # calcs sitting on top of the entry fields. Should I remove them prior to conversion?

What about opener scripts. Mine cause the main file to open, so that the user can't bypass the main startup script.

Also, should the passwords be removed until I get the converted files working?

Thanks, Steve

Steve, please let me know when you solve all these problems.

Speaking from a position of abysmal ignorance, I think you (we) have a major problem in converting runtimes. My updates consist of a rename and an import (into the new version.) Works like a dream. You cannot import from V5 or 6 into V7. You have to convert the old stuff first. Catch-22!! At first sight, it looks as though we might have to do an upgrade in the old version that exports all the old data as CSV or TAB or similar and then import that into a V7 copy.

I have had a quick look at conversion for my biggest customer - they use V6 not developer. Apart from the rotten (unusable) result from text on coloured backgrounds, the biggest problem looks like being passwords. This is mostly because their passwords are a bit of a mess now - mixtures of uppercase and lowercase, inconsistency of access, etc. Also , a nit but a nuisance nit - when I open a converted file on my own machine it always comes up with me ("Paul Jeremy" the W2K user) as the account name; this has to be replaced with the relevant password. There is probably a way around this; I haven't investigated thoroughly yet.

Paul, see my separate post in this forum called, "How stupid can they be?"

Steve