![]() ![]() The conversion is really not good idea now. I'm sure more questions will arise later. Of them, all the labels and text-entry boxes look exactly as they should with exactly the colors they always had.) not in the DOS-style windows opening on top Back to problem 4: If I have to use the BACKCOLOR and FORECOLOR properties to make the controls appear properly, will I have to do this on every single text control individually? (On our basic screens, i.e. I have done a little programming for Access recently, and there one has a key (F2 as I recall) that takes you straight to the Visual Basic code behind what you built graphically. To know about VFP", but I have no idea if it will help. I have ordered a book entitled "1001 things you always wanted The latest one I have is for VFP 6 (which I wound up never programming in). Back to problem 2 again: I can find no reference book that shows what the various new controls look like in code. (d) Esc or a button designed to close the window works, but the 'X' at the top hangs FoxPro and one must kill it via Task Manager.ĥ. (c) The buttons on them show only the button labels, no raised control - here I suppose we could just hard-code the The mouse over a control, either all the text labels disappear while leaving the controls, or more often EVERYTHING ON THE WINDOW disappears. The DOS-style windows (via DEFINE WINDOW and ACTIVATE WINDOW commands) act strangely: (a) They seem to entirely ignore all COLOR SCHEME parameters even though this is allegedly included in VFP for backward compatibility. Far too many for the client to be willing to pay for.Ĥ. But how do I even use them? Is it impossible without creating a form? This would mean LOTS and LOTS of Can I mix the newer controls with the old type? For example the textbox control has a century property that should fix problem #2 just above. After entering dates via GET in MM/DD/YY format the full MM/DD/YYYY date is echoed back. All dates and numbers show up in 'reverse video',Ģ. In all our printed reports, which use SAY commands, the simple text shows up either as yellow (on an ink-jet color printer) or so faint it cannot be read (on a black & white only laser printer). I also have only FoxPro 2.5 programming experience, no VFP.ġ. What we want is for itĪll to work as closely as possible to how it worked before without a huge programming task, which my client would never pay for. ![]() The great bulk of the interface consists of simple SAY and GET commands, including all reports. For example there is currently not a single SCX form in the whole application, and relatively few (DOS-style) windows. Re-writing this application using now standard VFP capabilities is totally out of Now my client wishes to switch to Win 7 (we have still not managed to get it working in a virtual XP even with the help of a local computer guru company). It has grown in the ensuing three decades to a VERY LARGE application, while still in FoxPro 2.5, and has remained so all the The application I have to convert is one I started writing for my client in about 1983, when 'FoxPro' was still dBase 2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |