Just my $.02 US: Go ahead and develop the new app in VFP6. Any files that are used solely by the Cash Management system can be put into your DBC. Any others can be FPW files, which VFP reads/writes just fine. The biggest 'gotcha' is that if you ever do a 'modify structure' in VFP on the FPW tables they will be saved as VFP tables. Second biggest (IMO) is that you can't use Transactions on non-DBC tables. This probably won't be a problem for you since you're used to working with FPW anyway. However, you can set buffering and most other VFP functionality.

When it's time to move everything into VFP, then all the tables can be brought into DBCs and you can update the code with Transactions where it wouuld be useful.

HTH
Barbara

>Hi,
>wondering if anyone has any ideas on the following.
>We have an accounts app (Sales,Purchasing,Gen ledger) written in FPW 2.6 which we are currently upgrading to VFP 6 (Estimated complettion date arounf Dec 2000)
>
>We have an urgent need to develop a Cash Management system for our existing FPW 2.6 users, but will also need this in VFP.
>I am wondering waht's the best way to go. I dont want to have to have to develop the Cash app in FPW and then rewrite it for VFP.
>
>What I would 'like' to do would be something like:
>
>- Develop the system in VFP
>- Somwhow, have access to the system from our FPW apps
>(e.g. Inputting a Payment in FPW will need to update Cash/Bank files)
>- All our files in VFP rewrite are in .DBC format.
>- The access from our existing FPW apps will probably be minimal requiring updates of Cash files during entry/creation of cheques
>Most processing will be done within the new App.
>
>I'd appreciate any comments anybody may have on this topic.
>
>Regards,
>
>Gerard