Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. USMA99

    VFP Radio Buttons

    Glad I could help, even if I didn't do anything. ;) I'm assuming the second option group has a button count of 2 or higher and your code is in an event that is actually firing. I put the code in the click event of a button but there are plenty of other events I could have used which might not...
  2. USMA99

    VFP Radio Buttons

    That exact code is working for me, on VFP9sp2. I don't call a refresh, but have you tried that?
  3. USMA99

    VFP Radio Buttons

    On it's face without other context, this should work to change the selection. What are you experiencing?
  4. USMA99

    SET('DEFAULT') Not returning drive and path for default directory

    Pretty lively forum here ... I'd say if fox never gave the full path and the help never said otherwise, drive-letter-only is WAD for SET('DEFAULT'). Nice tip on SET('DIRECTORY') ...
  5. USMA99

    SET('DEFAULT') Not returning drive and path for default directory

    At least in the experience of some, SET('DEFAULT') returns only the drive letter rather than the drive letter and path as expected, such as SYS(5) & SYS(2003) or FULLPATH(SET('DEFAULT')) would. There is some conjecture that this is windows-related, or perhaps not, per 1814250 Does anyone...
  6. USMA99

    path or cache/memory issue in VFP9

    Apparently I'm missing some historical context. And that's ok. Mike, It would be beneficial to the greater good to fully pin down how the program cache works and determine and/or resolve SET('DEFAULT'). If the latter isn't windows, then why not? Also, I don't think this thread subject would...
  7. USMA99

    path or cache/memory issue in VFP9

    Mike - While I don't know what prior discourse on modularity you're referring to, I wouldn't disagree with you ... it is definitely better form to never call 2 pieces of code the same thing. Your suggestion of naming the program by incorporating the job# was a countermeasure that occurred to...
  8. USMA99

    path or cache/memory issue in VFP9

    Many thanks, there's a lot of good stuff there. In following your reference to the CLEAR command in help, I found this also: and further: So, I've been using CLEAR ALL incorrectly since the 90s, thinking that it, well, cleared all. Using CLEAR PROGRAM like this resolves the issue when not...
  9. USMA99

    path or cache/memory issue in VFP9

    In a job shop setting I have a template folder structure with some starter programs in various locations, a fresh copy of the tree is used for each job. This means we have a prg in the corresponding folder under each job folder with the same name. Like: P:\ABC\001\some.prg...
  10. USMA99

    Can't Close VFP9 File Lock to Exe

    Ok, I think I'll make a "program that calls a program with the RUN command so that Windows is handling it. Mike, That last tidbit is interesting. So, instead of running as: "DO fxpname" You're saying I'm better off making one big fat exe and getting at the programs via a passed...
  11. USMA99

    Can't Close VFP9 File Lock to Exe

    We are calling the exe as "DO exename". My understanding is that we would be running local instances of the the program; at least with the fxp files I'm all but 100% sure this is the case as we can run multiple instances of them simultaneously. Perhaps EXEs and FXPs differ in this regard?
  12. USMA99

    Can't Close VFP9 File Lock to Exe

    We're experiencing a problem where we use VFP9 to call an exe (also compiled VFP 9) on a network location and it holds onto that exe file until FoxPro itself is closed. Until the person who called it closes FoxPro, you can't rename, delete, or overwrite, the exe. We've tried the usual close...
  13. USMA99

    Validate FoxPro Field Naming Constraints

    Thanks gents
  14. USMA99

    Validate FoxPro Field Naming Constraints

    Hello, Easy one here. I'm sure this has been done many times over and want to avoid reinventing the wheel but I can't find it using the forum search... We're looking for a procedure to see if a string is valid for use as a field name (not in a DBC). Essentially, this means it must contain...
  15. USMA99

    32-bit VFP9, 64-bit OS, and more than 4GB RAM

    Thanks for the input all. If anyone has first-person experience on the 64-bit & RAM question please let me know. I'll post what I find when I test this but it won't be for some months.
  16. USMA99

    32-bit VFP9, 64-bit OS, and more than 4GB RAM

    That last most had a typo, it should have read "... also note that we're discussing VFP version 9
  17. USMA99

    32-bit VFP9, 64-bit OS, and more than 4GB RAM

    Just to reiterate for everyone who keeps bringing it up, I'm very clear that I can't open a single table larger than 2GB. I know this is an internal fox issue and not a RAM issue. To paraphrase the last poster: VFP is a memory hog and will grab all of the memory that it can. To me, this is...
  18. USMA99

    32-bit VFP9, 64-bit OS, and more than 4GB RAM

    To a couple of your points: Our needs are that we run the dbf through a software package. (It qualifies records to meet USPS deliverability requirements and add's ZIP+4 data, etc) It's niche to our industry but a pretty first-rate and commonly used package. It parses the data within certain...
  19. USMA99

    32-bit VFP9, 64-bit OS, and more than 4GB RAM

    Some background: We use large free tables in a processing-intensive environment. We would LOVE to see the 2GB barrier eliminated ... but that's the subject of another post. Before you tell me to take this out of Fox and move into Oracle or SQL Server or something, note that other data...
  20. USMA99

    file 'foxtools.fll' does not exist

    thanks guys, there was a combination of two things: -There were search path issues preventing the file from being found and in copying the fll we found in the first place (so we therefore do the copy) I'm not sure we want to put the old fll in the new VFP9 search path in any event. -the...

Part and Inventory Search

Back
Top