Hello Kevin > how far up the support chain have you raised this ? > one of the things mentioned in the UK DevCon presentation was that YOU > end up setting the priority ? and InterSystems will try to do anything > to resolve the issues - it would be interesting to see just how far and > how quick they will move things.
It's HIGH now, but this afternoon I succeeded compiling, with some luck (almost by chance). I moved all our queries and views into separate classes, to be compiled at the end: I've discovered that this is a must only if the query uses more than the current table. If not, there's no need to move it. I made a loop which compiles all the classes one by one, with "ru" flags, and when the compiler stops we fill in the CompileAfter statement with the class which is not found. This was not enough, we still have experienced many errors. After tweaking with CompileAfter statement for two days, by trial and error (without a particular method), the loop now is able to compile everything, though I'm not sure I could do it again. A strange fact is that we can only compile using a loop (which scans classes alphabetically), but if we use $System.OBJ.CompileAll() there are errors (can't find some class). > > if you can't compile the classes after four days, then you have a > problem . . . > Now I can compile, but tomorrow I'll have to add 20 new classes...our customer is waiting, and I don't know how much time it'll take to compile after the last changes. I'd prefer that ISC starts looking for a serius fix, we can't go on with workarounds any longer...in the last year the time we take to compile has raised from one hour to 2/3 days...as we add new classes, new dependencies and errors appear...and it only takes 20 minutes, if you find the right sequence! Thanks a lot to everybody Max
