>Im moving development from 5.0 to 6.0, with a few users piloting my 6.0 versions of a long running app. I need to distribute 5.0 apps to other users probably for about 5 more months.
>
>Whats the best way to install 6.0 on my machine so I still can develop in 5.0 as well?
>
>TIA
>CG

Chris;

When VFP 6.0 came out I converted a VFP 5.0 app for a client. That was the first day of release of VFP 6.0. There were two errors due to code I used that VFP 6.0 did not like. As I recall in was a Y2K (gee – I thought and wished I would never hear that term again!) issue because in one case I used CTOD() in code for one report. By using Set Strict Date, Set Date and Set Century, all was well. The second problem was also related to Set Strict Date. It only took a few minutes to discover and resolve this issue. Since that time I have not used VFP 5.0 and will not do so. Amazing how VFP 5.0 did not care and VFP 6.0 “did not allow it”!

By the way - VFP 5.0 IMO is the product that VFP 3.0 should have been! VFP 5.0 was solid compared to VFP 3.0 (flaky at best).

Microsoft tells us there is “no problem using VFP 5.0 and VFP 6.0 on the same machine. That may be the case but I have several computers and I use removable hard disks in trays. I keep only one version of a development tool on a hard disk. That is my preference and when I am at home I do things the way I like. I also have each client on an individual hard disk. I keep backups of all client work. Again, this is just the way I like to do things.

The other day I had my first hard disk failure – on a major clients hard disk. Guess what? I practice what I preach as I got a new hard disk and used my back up to reload the disk. I keep two backup sources. One on a master hard disk on one machine and one on a Zip media.

Going to VFP 7.0 will be fun and when I do I will no longer use VFP 6.0 – unless you (the client) want to pay me to go backwards.

Tom