>I'm rewriting my networked mailorder business application in VFP5 on my notebook computer. This application is now written in FoxPro 2.0. I want to gradually add VFP5 modules to the network application and thus mix the platforms. I hope to accomplish this by using views to local free tables in VFP5 Database containers. Then, when the time comes to switch everyone to use only VFP5 programs, I'll convert the views to database container tables.
>
>Any comments on right or wrong thinking would be appreciated.
>
>The directory structure on the network is as follows:
>
>data is stored in J:\DB\DATA
>programs are stored in J:\VFP5\PROGRAMS
>forms are stored in J:\VFP5\FORMS
>classes are stored in J:\VFP5\CLASSES
>etc...
>
>How do I assure that when we move everything to the network, all pointers will be mapped to the right directories? Do I just replicate these structures on the C: drive?
>
>Thanks in advance.

When you move project from one drive to another it goes smoothly as long as you keep all project included components (reports, forms, etc.) on relative paths i.e. project file in root folder and components in subfolders. Data files generally are not included in project and real location should be checked in run-time, usually by resetting DataEnvironment.Cursor.Database properties for dbc-tables and DE.Cursor.CursorSource for free tables.