D
dbeavon
Guest
Yes that is useful. I will look for that and, if I see a source file being opened, and a subsequent 300 ms delay then I will know who to blame. 
This is very helpful. I've also used procmon (sysinternals) in the past to see whether source or r-code was being opened, but it is much easier when everything is in the same client log instead of cross-referencing across two logs. Still, it would be better if there was a log entry type for compiler operations. I'm surprised that it is missing, considering that there are other log entry types for lots of other minor activities that are happening in an ABL session. FYI, your name came up in a conversation today with my tech support engineer. It was in regards to this post from two years ago: community.progress.com/.../33923 We supposedly have a fix now for "stale schema" issues in remote (client/server) connections, but it still doesn't behave exactly like the self-service connections. In the remote connection we still see a system error message ... the only difference in the oe 11.7.5 sp is that the remote ABL client doesn't crash after showing the error. Personally it worries me if a client application does NOT crash after it generates a scary system error about "stale schema". What is the alternative to crashing? Just winging it?
Continue reading...
This is very helpful. I've also used procmon (sysinternals) in the past to see whether source or r-code was being opened, but it is much easier when everything is in the same client log instead of cross-referencing across two logs. Still, it would be better if there was a log entry type for compiler operations. I'm surprised that it is missing, considering that there are other log entry types for lots of other minor activities that are happening in an ABL session. FYI, your name came up in a conversation today with my tech support engineer. It was in regards to this post from two years ago: community.progress.com/.../33923 We supposedly have a fix now for "stale schema" issues in remote (client/server) connections, but it still doesn't behave exactly like the self-service connections. In the remote connection we still see a system error message ... the only difference in the oe 11.7.5 sp is that the remote ABL client doesn't crash after showing the error. Personally it worries me if a client application does NOT crash after it generates a scary system error about "stale schema". What is the alternative to crashing? Just winging it?Continue reading...