Search results for query: *

Hi All, One of my FoxPro 2.6 / Windows apps is acting up on Windows XP Professional -- whn the user starts a certain file import process, she gets the error "FoxPro caused a general protection failure in module WIN87EM.DLL", but only the first time after booting the computer. The app is closed...

It did help, as it made me track the 'on error' lines in the script ; a bit more googling gave me the complete solution when it came down to handling the user clicking 'Cancel' : http://word.mvps.org/FAQs/MacrosVBA/PseudoBeforeClose.htm Thanks again, Jan Schenkel.

For our administrative dept, I'm working on a simple document management tool that will save backup copies of Word files in a pre-determined path, if a user-property has been set. Since Word doesn't have a Document.SaveCopyAs method, I have to first Save the current document, then SaveAs to the...

Hi, As FoxPro is still copyrighted software, you will have to buy a legal copy. Check Ebay or surf to http://www.emsps.com/oldtools/msfox.htm Hope this helped, Jan Schenkel. "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)

Hi Cesar, An alternative approach is to setup an ODBC connection to a special DBF file you write the necessary data to and then close from Fox, and then have Excel connect to that DBF, update the contents of its own cells and redraw the graph. Just a thought, Jan Schenkel. "As we grow...

Hi All, Here's something I had been struggling with yesterday; I just thought I'd share the solution with you. The problem started when one of our users tried to enter the articles in our invoicing program by scanning the codes in via a barcode scanner. The program constantly returned the...

Hi Enrique, This sometimes happens to me as well, though mostly when I'm working with reports. My best guess is that as I go through numerous cycles of 'rebuild project' + run main program, the memory is gets filled up with arrays and other large variables. When I quit and start FoxPro again on...

Hi MDoom, The trick we use, is to add PROCEDURE ButtonSet ** enable/disable buttons before READ statement SHOW GET m.TheButton DISABLE RETURN .T. And then change the READ statement to READ <other params> WHEN ButtonSet() This way, the buttons are enabled/disabled just before the...

Hi, Michael stated a key issue here: do you _legally_ own the application code? Does the license agreement you signed grant you the rights to the code? I know our license agreement specifically FORBIDS the decompiling/reverse engineering of applications we write, even if it is a customised...

Hi Mike and Scott, I've been lookling through the FoxPro documentation for info on working with Popups that aren't ScreenGenned so to speak. Thanks for pointing it out to me. I always thought that those DEFINEd menus were only for the menubar, but appearently not -- I guess I've been spending...

Hi all, I've come to a snag that I'm not sure how to address. On a screen I want to display a popup of about 17 lines, including dividers. This list is longer than 255 characters, and that's where the trouble starts. So instead of defining the options directly in a PICTURE clause, I define the...

Hi Jane, My first thought would be to do this from within the WHEN clause of the object. You could call a generic routine for this along the lines of FUNCTION FocusOn SHOW GET _CUROBJ COLOR SCHEME <A> RETURN .T. In order to remove the hilite color, you'd have to adapt the VALID clause of the...

Hi Indarto, One other option would obviously be to -copy the project file and source into another directory, -fiddle the settings of the project a bit, -have your two config.fpw files pointing to the two different directories You'll have some synchronising to do just before testing, but it...

Hi, Just thought I'd add that FoxBase/Plus 1.0 and 2.0 also existed for Mac, as well as FoxPro versions 2.5 and 2.6 ; and the last version for Mac was Visual FoxPro 3.0 I'm also sure there were Unix versions for FxoPro 2.5 and 2.6 ; don't know about before then. Ah, the memories :-) Not to...

Hi Nasrin, After you mlade your index using INDEX ON theField TO theField.idx did you also run a SET INDEX TO theField.idx afterwards? Otherwise, there is no 'live' link between the data and the index file. If that doesn't help, it could be that the active index file is overridden by...

Hi jrbbldr, Actually, we ordered our FoxPro 2.6 /Mac there last october, as the programs compiled with FoxPro/Mac 2.5 proved horrendously unstable on recent machines. Service was prompt and good ; so if you're looking for older versions, definitely consider them. Best regards, Jan Schenkel...

Hi blazblaz, When FoxPro 2.x was released back in 1992 (93?), the programmers weren't even thinking about Y2K issues -- and if they were, they figured you'd have updated your program with a later version by now :-) As it states in the documentation, the program will always assume the 20th...

...&quot;As we grow older, we grow both wiser and more foolish at the same time.&quot; (De Rochefoucald) ---- Code snippet ---- PROCEDURE pDatY2K ** Define preprocessor variables #DEFINE _c_Y2KBase 1960 ** Define local variables PRIVATE theObject, theDate theObject = OBJVAR() && by default...

The &quot;invalid .exe&quot; errors are probably due to the fact that Intel and Motorola processors use different bit-sequences to store binary information (known as the Little Endian vs Big Endian issue) I'd suggest moving the .exe onto the client machines. Granted, it gives you...

Hi Shadow38X, That puts things in a different light -- I've been able to get things working properly, but the headaches were quite serious :-) Okay, most important question, can the PCs access any other files? If so, it could be that the path to the dbf files is hard-coded, and you may need to...