The information in this article applies to:
SUMMARYThis article discusses ideas for implementing a cross-platform solution between Microsoft Visual FoxPro 3.0 for the Macintosh and Microsoft Visual FoxPro 5.0 or 6.0 for Windows. MORE INFORMATION
You can create a cross-platform solution between Visual FoxPro (VFP) 3.0
for the Macintosh and Visual FoxPro 5.0 or 6.0 for Windows in different
ways. For example, one of the following situations may apply:
What to Do with the DataData between Visual FoxPro 3.0 for Macintosh and Visual FoxPro 5.0 or 6.0 for Windows is completely transparent with the exception of stored procedures. To avoid conflicts with stored procedure code, place it in a program outside of the database and access it when needed using SET PROCEDURE TO cProcedureProgram. You can open both a Visual FoxPro 3.0 for Macintosh or a Visual FoxPro 5.0 or 6.0 for Windows .dbc file without distinction. One recommendation would be to modify the .dbc file in Visual FoxPro 5.0 or 6.0 for Windows, so you can have access to the new data features. Another option would be to keep the .dbc file in Visual FoxPro 3.0 for Macintosh format (with the appropriate stored procedures) and use the data in Visual FoxPro 5.0 or 6.0 for Windows by using the ODBC driver.What to Do with Project Files, Forms, Reports, and So ForthCreate two different applications from the same source files. The best way to do this is to have two projects in the same directory (folder) accessible by both platforms, the one for the Macintosh in Visual FoxPro 3.0 format and the one for Windows in Visual FoxPro 5.0 or 6.0 format. You need to add only Macintosh- specific files (CFM libraries, PICTS, AppleScript files) to the Macintosh project--same idea with Windows (specific DLLs if needed).Additional query words:
Keywords : kbinterop kbVFp300 kbVFp500 kbVFp600 |
Last Reviewed: December 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |