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!
Compilation
- Thread starter alisaif
- Start date
Olaf Doschke
Programmer
You can start the debugger and open the debugout window. You can see details of compiplation listed in there, every file being compiled.
If compilation hangs, you see what hangs.
A good thing to do before compilation is CLEAR ALL or even restat VFP. Hanging compilation because of classes still residing in memory can be prevented that way.
Bye, Olaf.
If compilation hangs, you see what hangs.
A good thing to do before compilation is CLEAR ALL or even restat VFP. Hanging compilation because of classes still residing in memory can be prevented that way.
Bye, Olaf.
- Thread starter
- #3
No, No I am sorry I couldn't deliver the right object to you.
I just wanted to see the progress bar on the screen and other information related to the project ("means what file is compiling") in the status bar at the time of compilation. I think some "SET" command is needed for that.
I hope you got it.
Thanks
Saif
I just wanted to see the progress bar on the screen and other information related to the project ("means what file is compiling") in the status bar at the time of compilation. I think some "SET" command is needed for that.
I hope you got it.
Thanks
Saif
Mike Lewis
Programmer
Using the Debugger will certainly solve the problem, but keep in mind that the compilation is likely to be slower while the Debugger is open.
As well as doing CLEAR ALL or restarting VFP as Olaf suggests, it is a good idea to clean up the various files in the project. For the project itself, select Clean Up Project (on the Project menu). For forms and class libraries, open the files as DBFs (with USE), and then pack them. You don't need to do that before every compile, but it's worth doing once in a while, and especially after you have done a lot of development on a particular file.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
As well as doing CLEAR ALL or restarting VFP as Olaf suggests, it is a good idea to clean up the various files in the project. For the project itself, select Clean Up Project (on the Project menu). For forms and class libraries, open the files as DBFs (with USE), and then pack them. You don't need to do that before every compile, but it's worth doing once in a while, and especially after you have done a lot of development on a particular file.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
Mike Lewis
Programmer
Have you got SET STATUS BAR ON?
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
Mike Lewis
Programmer
Here's a little utility that I think will do what you want:
It compiles all the files in the project, displaying the name of each file in a Wait window as it does so.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
It compiles all the files in the project, displaying the name of each file in a Wait window as it does so.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
Olaf Doschke
Programmer
I didn't knew you could turn that usual progress window of the build off or have some settings turning it off. If I SET STATUS BAR OFF the build will show steps in a wait window instead.
Do you have multiple screens? The build progress window could show up on another display.
Anyway, if you have a hanging compilation, the debugger debug out window is your best way to find out the reason and the file hanging.
Bye, Olaf.
Do you have multiple screens? The build progress window could show up on another display.
Anyway, if you have a hanging compilation, the debugger debug out window is your best way to find out the reason and the file hanging.
Bye, Olaf.
- Thread starter
- #8
Olaf Doschke
Programmer
You seem to have a database in your project, that is used by users.
PACK only works on a dbc in exclusive mode.
Somehow Compile also compiles the DBC as part of your project and can't PACK it beforehand.
Remove that DBC from your project during build.
In the long run you should have a separate DBC fpr development and not the one DBC the app finally works on. That's just an assumption I have, because who else would have the DBC opened but users.
If that's not the case I already said CLEAR ALL would help, it does not only clear classes residing in memory, it also closes workareas and DBC. You also should collapse the database node of the project manager, otherwise the DBC is open,
Bye, Olaf.
PACK only works on a dbc in exclusive mode.
Somehow Compile also compiles the DBC as part of your project and can't PACK it beforehand.
Remove that DBC from your project during build.
In the long run you should have a separate DBC fpr development and not the one DBC the app finally works on. That's just an assumption I have, because who else would have the DBC opened but users.
If that's not the case I already said CLEAR ALL would help, it does not only clear classes residing in memory, it also closes workareas and DBC. You also should collapse the database node of the project manager, otherwise the DBC is open,
Bye, Olaf.
Mike Lewis
Programmer
The program I suggested does indeed attempt to compile a database. That may or may not be what you want. For example, you might have stored procedures in the database that need to be compiled.
If that's so, the solution is to make sure the database is closed before you do the compile. And the way to do that is to close the project first. As long as the project is open, there is a chance that any databases contained in the project will also be open. That's because the project has to know which tables (and views, stored procedures, etc.) are contained in the database.
So, close the project, then do CLOSE DATABASES ALL in the command window, then run the utility.
Alternatively, you can avoid compiling the database by making a simple change to the utility. Around line 70, you will see the command to compile the database. Simply comment out that line.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
If that's so, the solution is to make sure the database is closed before you do the compile. And the way to do that is to close the project first. As long as the project is open, there is a chance that any databases contained in the project will also be open. That's because the project has to know which tables (and views, stored procedures, etc.) are contained in the database.
So, close the project, then do CLOSE DATABASES ALL in the command window, then run the utility.
Alternatively, you can avoid compiling the database by making a simple change to the utility. Around line 70, you will see the command to compile the database. Simply comment out that line.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
- Thread starter
- #11
Olaf Doschke
Programmer
Repeated:
1. CLEAR ALL
2. collapse the database node of the project manager
Then build.
Bye, Olaf.
1. CLEAR ALL
2. collapse the database node of the project manager
Then build.
Bye, Olaf.
Mike Lewis
Programmer
YOU are using it. The database is open in your development environment. You can confirm that by glancing at the combo box in the middle of the standard toolbar. If it shows the name of the database, then the database is open (you might need to actually drop down the combo in order to see the name).
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
- Status
Similar threads