There's apparently a limitation on how much stuff you can cram into FPD26 Standard Project Manager. I inadvertently forgot to load FPD26 Extended for a previously perfectly operating application, and found the Project Manager wouldn't let me REMOVE files (although I could ADD new ones), and I couldn't change any Screen Set Code Options. This is the kind of thing that's making me go bald!
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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
FPD26 Project Manager 1
- Thread starter Jerry4DOS
- Start date
- Status
Obviously, you are running FP DOS's standard version under Windows, or if really in DOS you don't have a compatible Expanded Memory Manager (EMS). We all have to live with limitations when running under alternate environments than that for which a product was designed for and tested under.
Rick
Rick
-
1
- Thread starter
- #3
Jerry,
It sounds like the Project itself may be corrupted. I've experienced this numerous times. Even if you move the project to a new machine, you will get the same behavior. Try (and this can be a pain if you have certain tables Opening & Closing files, since that info is saved at the Project Level) rebuilding your project from scratch. I know it can be a pain, but it may be your best bet to solve your problem.
The 106th issue sounds very fishy to me, as I have had Fox Dos project in excess of 120 files associated.
The only other thing I can recommend is, if you have dSalvage, you can make a copy of your project files, and try to "Fix" them under dSalvage. This may, or may not work. What you would do is:
COPY MYPROJ.PJX MYFIX.DBF
COPY MYPROJ.PJT MYFIX.FPT
Then, run dSalvage against the MYFIX.DBF. It will find the associated memo file automatically. If it "Fixes" anything, rename it to:
RENAME MYFIX.DBF MYFIX.PJX
RENAME MYFIX.FPT MYFIX.PJT
Thanks,
-Scott
s-) Please let me know if this has helped s-)
It sounds like the Project itself may be corrupted. I've experienced this numerous times. Even if you move the project to a new machine, you will get the same behavior. Try (and this can be a pain if you have certain tables Opening & Closing files, since that info is saved at the Project Level) rebuilding your project from scratch. I know it can be a pain, but it may be your best bet to solve your problem.
The 106th issue sounds very fishy to me, as I have had Fox Dos project in excess of 120 files associated.
The only other thing I can recommend is, if you have dSalvage, you can make a copy of your project files, and try to "Fix" them under dSalvage. This may, or may not work. What you would do is:
COPY MYPROJ.PJX MYFIX.DBF
COPY MYPROJ.PJT MYFIX.FPT
Then, run dSalvage against the MYFIX.DBF. It will find the associated memo file automatically. If it "Fixes" anything, rename it to:
RENAME MYFIX.DBF MYFIX.PJX
RENAME MYFIX.FPT MYFIX.PJT
Thanks,
-Scott
s-) Please let me know if this has helped s-)
Jerry,
Sorry for the "bad" assumption, very few people are still actually running DOS.
I'll have to agree with Scott, sounds like something is corrupted. The last major project I worked on in FPD 2.6a (in both Standard and Extended modes) had the following numbers: Program - 164, Screen Set - 149, Menu - 3, Report - 122, Label - 4, Library - 5, Other - 13. And amoung the Others were 4 additional APPs!
Rick
Sorry for the "bad" assumption, very few people are still actually running DOS.
I'll have to agree with Scott, sounds like something is corrupted. The last major project I worked on in FPD 2.6a (in both Standard and Extended modes) had the following numbers: Program - 164, Screen Set - 149, Menu - 3, Report - 122, Label - 4, Library - 5, Other - 13. And amoung the Others were 4 additional APPs!
Rick
- Thread starter
- #6
Thanks Scott and Rick:
This is not a big problem -- everything works fine in FPD26 Extended, which is where I usually work. No corrupted files, and nothing needs to be fixed. Scott planted a seed in my brain, though: maybe I've been transporting something "bad" in my project from computer to computer for my tests. So, we started over and conducted JERRY'S SCIENCE FAIR PROJECT:
I loaded FPD26 STANDARD, started in a clean directory, created 125 brand new PRG files (named FILE0001.PRG through FILE0125.PRG), with a single line of code (? "Say this"
in each file. Then I made a MAIN.PRG with "DO FILE0001", "DO FILE0002", etc., adding files to MAIN.PRG one at a time, having the Project Manager REBUILD PROJECT each time. With each BUILD, I checked to see if I could REMOVE FILE0001 from the project, save the project with ctrl+w, then reload the project with MODIFY PROJECT MAIN. After adding FILE0112 to the project, I could no longer really REMOVE any files. The REMOVEd file disappeared from the PROJECT MANAGER window, but after saving and reloading the project, the REMOVEd file reappeared. The magic number of project files seems to be 112 (not 106 as reported earlier). I also checked this out using FPD2.5a with the same result. Note that this is not a complete failure after #112 -- the Project Manager still compiles large (120+) APPs and EXEs that work perfectly. Scott may have had this problem with his 120+ file project and never realized it unless he tried to REMOVE a file or change a Screen Set Code Option.
The bottom line is, this is just a "heads up" in case your Project Manager starts behaving strangely some day. Maybe you'll remember this thread and you'll know how to work around this little FoxPro anomaly. Thank to all.
Jerry
This is not a big problem -- everything works fine in FPD26 Extended, which is where I usually work. No corrupted files, and nothing needs to be fixed. Scott planted a seed in my brain, though: maybe I've been transporting something "bad" in my project from computer to computer for my tests. So, we started over and conducted JERRY'S SCIENCE FAIR PROJECT:
I loaded FPD26 STANDARD, started in a clean directory, created 125 brand new PRG files (named FILE0001.PRG through FILE0125.PRG), with a single line of code (? "Say this"
in each file. Then I made a MAIN.PRG with "DO FILE0001", "DO FILE0002", etc., adding files to MAIN.PRG one at a time, having the Project Manager REBUILD PROJECT each time. With each BUILD, I checked to see if I could REMOVE FILE0001 from the project, save the project with ctrl+w, then reload the project with MODIFY PROJECT MAIN. After adding FILE0112 to the project, I could no longer really REMOVE any files. The REMOVEd file disappeared from the PROJECT MANAGER window, but after saving and reloading the project, the REMOVEd file reappeared. The magic number of project files seems to be 112 (not 106 as reported earlier). I also checked this out using FPD2.5a with the same result. Note that this is not a complete failure after #112 -- the Project Manager still compiles large (120+) APPs and EXEs that work perfectly. Scott may have had this problem with his 120+ file project and never realized it unless he tried to REMOVE a file or change a Screen Set Code Option.The bottom line is, this is just a "heads up" in case your Project Manager starts behaving strangely some day. Maybe you'll remember this thread and you'll know how to work around this little FoxPro anomaly. Thank to all.
Jerry
Jerry,
Interesting point. You have hit the nail on the head! I went back to an old project under 2.6a, in DOS and tried to remove a screen set, and got the same behaviour! (Interesting).
In all of the Fox 2.x versions, I've encountered so many problems that are related to corruption in the Project file. They are so suseptable to weird behavior. God forbid your machine crashes while you've got a project file open... you are doomed to troulbes when you start it back up. Thanks for the little tip though.
Thanks,
-Scott
s-) Please let me know if this has helped s-)
Interesting point. You have hit the nail on the head! I went back to an old project under 2.6a, in DOS and tried to remove a screen set, and got the same behaviour! (Interesting).
In all of the Fox 2.x versions, I've encountered so many problems that are related to corruption in the Project file. They are so suseptable to weird behavior. God forbid your machine crashes while you've got a project file open... you are doomed to troulbes when you start it back up. Thanks for the little tip though.
Thanks,
-Scott
s-) Please let me know if this has helped s-)
- Status
Similar threads
