Thanks Chris for info. I know that using the "&X" macro is really using the compiler for one line of code. The rest of my program is sequential processing of lines of text. Conditionally jumping to line numbers of text and back. Conditionally skipping lines of processed text.
What was the...
I create EXE by compiling the project.
I run macros via commands such as:
X=[ Wait "Hello World" Window]
&X
Do While, For Next etc are simple operations on text variables.
I use "Do ProcedureName" commands for running my procedures includes in EXE program.
ExecScript() is only since VFP7...
I use one EXE file for all my applications. Program EXE processeses (interprets) commands saved in the memo fields. Fox-Pro (since version 2.0) turned out to be a very simple and good tool for this purpose. Thanks to this, I could correct code of my clients' programs and run programs without...
I started with MS Basic. I was programming for 8 bit microcomputers about 40 KB RAM, two floppy drives (8") and a printer. Atari 800 XL children's computer had better parameters.:)
In end of 80's Dbase II,III, Clipper DOS. A few years break for other systems (Turbo Pascal). In halv of 90's...
Thanks for the extensive explanation. The old project (DOS interface) is written in VP6. The second one with Windows interface in VP9. I moved the required code fragment to VP9, made some corrections. Tt'is slowly visible that it will be working.
There is a question. Is processing DBF tables...
Exactly as you say Chris. I just checked it. I added a lot of pictures to the EXE file (houses, forest etc). In the process manager RAM allocation did not change (7.5 MB). The EXE file has increased significantly (20 MB). If I used the pictures in the program the RAM allocation would probably...
It used to be possible to store overlays in EXE files. But that was in DOS. A fragment of the EXE was loaded into RAM. The main menu and other necessary things. The rest was loaded as needed. However, system reserved RAM for the largest overlay. That was the case in Clipper. I don't know how it...
Thank you. The project generating the EXE has only program code. I don't have any graphic files there. The differences in projects are in the user interface. One looks like DOS, the other is typical for Windows. Settings for individual applications are saved in DBF tables. Macros defining the...
Thanks all for the reply. I asked because my EXE files are not much bigger than 400 KB. I had problems in the past (Pascal Clipper). I've always tried to keep the code as small as possible.
I'm happy to hear your opinions. :)
My users like to have multiple Excel spreadsheets or Word documents...
Hi all.
I have 2 similar projects in VFP9. I would like to join them in one. I compiled them for a testing and the EXE file size was about 800 KB.
I would like to ask experienced colleagues. What is the safe limit size for EXE file in FVP9 ?
In one of the programs I used increments with a common table with the structure: TableName C 10, Counter N 10. This gave good results. It had as many records as there were tables requiring increments. The procedure opened the table, found the table name, set Rlock() until successful and...
Of course, very valuable advice. I have program that 100-200 users work on at the same time. However, I created DBF tables separately for individual departments (logistics units) in separate folders(30 folders) . Each table with main data contains 10-20 thousand records. Each table has own...
You are right Chris. I use VFP 6.0 in some of my programs. How can I do autoincrement, are there any way ? There is no Integer(Autoinc) field type. I moved some programs to VFP9 but I left SQL code.
@GriffMG, As for my system, I don't know ++XBase .
As for VDOSPLUS - XTREE doesn't work, Dos Navigator doesn't work properly. I have run my old warehouse program under Clipper 87. The screen was shifted to the right. Not all graphic elements were visible. As always, there are some problems...
Chris is 100% right. I advise you @tsibert to reorganize the table structures and add small ID fields (FIELD_ID). These will be index keys. In the "A" area, unique keys. In the "B" area, they will be repeated. Unique keys are easy to create in numeric ID fields (INTEGER). 5-6 characters are...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.