The final, final solution will likely involve a loop that builds up a number of PACK commands from a FileSet which then serves as the input into the Create ZIP File action. The - for now - final solution is to use the ADO Execute SQL action, uncheck the “Fail if 0 rows are affected” option and use the following SQL statement:ĮxecScript("USE %table% EXCLUSIVE"+chr(13)+chr(10)+"PACK") Although packing a table creates a new file without deleted records, the resulting table is still a FoxPro 2.6 DOS compatible DBF file.
Also fortunately, the old code to handle non-VFP types of DBF files is still part of the product. This doesn’t work with FinalBuilder, though, because FinalBuilder closes the connection.įortunately, EXECSCRIPT() is among the supported functions in the OLEDB provider. Can anyone tell me what Foxpro 2. You can use the Visual FoxPro Forms Designer to create the custom application startup screen. Step-by-Step Procedure for Creating a Custom Startup Screen. I am starting a Foxpro 2.6 project where I will have to create exes etc. This form will not suppress the FoxPro system menu or the FoxPro title bar when running within an executable file. Since the VFP OLEDB provider has an instance of VFP running it will just keep tables open in between commands. 16 Comments 3 Solutions 3819 Views Last Modified. In a program you could connect, send two commands separately and disconnect.
The code I want to execute isĪs you notice these are two code lines. Instead you have three actions:Įach action will connect to the database, execute the statement, do something with the results and disconnect. You can make a FoxPro exe if you will build it, located on the left side of the Project Manager On Build Action choose Rebuild Project, and on Option choose Recompile All Files.
FinalBuilder isn’t a full blown programming languages that would let you create a connection, use multiple command objects, and the like. FinalBuilder supports ADO to access tables, which means the OLEDB provider for Visual FoxPro gets used. Hence, whenever I can find a built-in solution with reasonable performance, I’ll use that. but forgot to compile an EXE on the build server and place it into the bin directory for the build project. More than once I made changes to a program, tested the EXE on my development machine and commited the changes to the SubVersion repository. FinalBuilder (which runs on a different machine than my development environment is, I must add) calls a compiled Visual FoxPro EXE. Some of my external programs are Visual FoxPro code. For my FinalBuilder scripts I prefer to use built-in solutions whenever possible.Įxternal programs aren’t totally banned here, but they add subtle problems. That’s a simple job in a FoxPro application. What we ship to our clients should not contain deleted records, so we need to pack them first. The import, as likely most imports do, involves updating, adding and deleting records. The standard version of Visual FoxPro lets you build executables and DLLs which can be freely distributed without paying additional licence fees. Every two weeks we get updates for these tables.