Recent content by Jerry4DOS

Here I am, 11 years into my life's "FoxPro Experience," and I turned up another "undocumented feature" of FPD2.6a I hadn't encountered before. I checked our forum SEARCH, and couldn't find it discussed earlier. You can't stuff the KEYBOARD with more than TWO...

Any time I had a memo field corruption, it was when I was using FDP STANDARD, never when I was using FPD EXTENDED. I even corralled and saved a couple of instances of predictable corruptions, but I never traced it down far enough to figure out exactly what triggered the corruption -- maybe some...

Put the cursor on the object you want to resize. Press CTRL+SPACEBAR, then use arrows to resize. Press ENTER.

Hi Martin: If you call the BROWSE each time with the entire code you've listed above, your BROWSE window will take on the attributes as you have listed them, not the way you modified your window by clicking and dragging (or resizing or whatever) after the window was displayed. You'll have to...

If you use ";" as a continuation character in a .PRG to keep the line from getting too long, don't put any "&& comments" on the line after the ";"

You might check out this thread: thread182-224837

In the same vein, ever notice that under certain conditions @...GET push buttons aren't highlighted (indicating which one gets activated when the ENTER key is pressed)? I've put this code in my screen "READ CLAUSES WHEN" which seems to fix it. CLEAR TYPEAHEAD KEYBOARD...

If you know the cursor is always starting in field #1 and you want it to move to field #8, it's easy: FOR i = 1 to 7 KEYBOARD "{tab}" ENDFOR If you don't know where the cursor is starting from: DO CASE CASE VARREAD() == "Xxx" FOR i = 1 to 7 KEYBOARD...

I've had good luck with this routine: I get my FOXUSER file just the way I want in development. Make a copy under the new name MASTUSER. Delete all the records except the ones that pertain to this application. Include MASTUSER in the standalone executable (which makes the file READ-ONLY)...

Unless you want to partition your hard drive into 2Gb (or smaller) chunks, you may be out of luck. See: thread182-12583

Seems to me I remember that SCAN...ENDSCAN works faster on an UNORDERED table -- might be useful if you're going to SCAN an entire table.

Hi DaleFrench: Are you absolutely sure there isn't more than ONE foxuser .dbf/.fpt resource file on the path? Things can get REAL squirrlley if your application finds one file sometimes, and a different file another time. Jerry

Have you tried using FoxProX? This may not help if your Windows DOS doesn't have any memory managers, though. Jerry

Hi xBaseDude: If you get 2¢, I get 2¢. If you use the PROJECT MANAGER, click the INFO button and look at how FPD displays dates later than Y2K! Jerry

Arev: You might check through your hard drive(s) to make sure there isn't more than one foxuser dbf/fpt. Some really strange stuff can happen if you've got two or more "on the path." Jerry