The Export-It application is designed to run on, and has been succesfully installed on, platforms with any version of Microsoft Windows® from NT or 95 through 2008 or 7. However, it is inherently a “32-bit” application and uses the “Windows® 32-bit API” environment that is available on all of these platforms. It is the responsibility of the administrator to ensure that the Export-It application components execute in such a 32-bit environment when it is installed on a native “64-bit” version of Windows® software.
But a distinction must be made between where Export-It performs only file access (Database "server" Folder) and where execution occurs. The Database "server" Drive may be on any platform capable of publishing a "share" using the basic “Windows Printer and File Sharing” [SMB] protocols; including Novell or Banyan file servers, Linux or UNIX platforms, Macintosh or A/UX machines or computers running Microsoft Windows® or DOS with LAN Manager®. But all execution (of code retrieved from the Platform "local" Folder—logically a distinct site even if physically on the same drive letter) must occur in a “Windows® 32-bit API” environment.
Export-It is also a native database management application. Which means that it depends upon "raw" file sharing, with the DataFlex® DBMS providing any required "locking" logic, using the “Windows Printer and File Sharing” [SMB] protocols for "network" drive access. "Helper" features, such as “Opportunistic Locking” facilities, are not required (and can interfere with a DBMS). In any version of Windows® where “Opportunistic Locking” is on by default, such as Windows® 2000 Server, it should be manually disabled for Export-It installations (just as required by Microsoft SQL Server applications).
When installed in a native “64-bit” version of Windows® then setup must ensure that the following components, located in the Platform "local" Folder, will execute in a “32-bit” or “XP” compatibility mode:
All "executables" (with extensions ".cmd", ".bat", ".exe" and ".com") must execute in “32-bit” mode. Even though console and batch commands use only a small subset of the API it must be the “32-bit” API.
Graphic, AKA "windowed", applications use a larger subset of the “Windows® 32-bit API” suite, but they also require a “32-bit” environment.
Located in the "VDF7" subfolder of the Platform "local" Folder (with ".vd7" extension) these modules are executed by the “32-bit” DataFlex 7 interpreter ("Dfrun.exe") in the same sub-folder.
Located in the "PROG" subfolder of the Platform "local" Folder (with ".flx" extension) these modules are executed by the “32-bit” DataFlex 3 interpreter ("Dfrun.exe") which is located in the root of the Platform "local" Folder.
If setting individual file “Compatibility” mode on “Property” dialogs then ensure that all of the files described above are flagged for “32-bit” or “XP” compatibility mode (although use of a 32-bit "virtualized server" is probably an easier way to ensure “32-bit” mode).
