BobyIsProgress
Member
So the check syntax inside a procedure of this procedure is pretty fast, instantaeous if i can say.The question remains why the compilation of this program takes an "enormous" amount of time, relative to a larger program. Though you haven't confirmed the size of all of the source involved.
Try to think of what is different about this particular program, compared with larger ones that compile much more quickly. Does it read its source from a different location than others (e.g. a network share versus a local directory)? Is the r-code saved to a different location? Does it connect to a database that is in a different place, e.g. a slower database server on a slower network? Or a larger number of databases? Or databases with much larger schema?
Does it take a similarly long time to do Compile | Check Syntax? I would expect that to be similar to a compile, apart from saving r-code. If it does, try tracing it with Process Monitor and see where the time is spent. If it doesn't, then trace the save operation.
I think it could be related to the number of temp-table I use (more than 10) and maybe the enormous quantity of data I charge inside.
I never did such a program with this much of temp-table before.
Also about the network and environnement, I have no issue or lag with the database itself even if she is on another server. The *.r is inside the same directory of the *.p file.
I think I will try to redo it from the start and see if I can detect when the compilation take to much time to be done.