Tansfer Project Logs - unhelpful

[Paolo F Cantoni]

When you ask for a log file for the transfer project functionality, if there is an error, you get a dialog indicating a bit about the error.  However, the log file contains LESS than is on the dialog.  This is less than helpful as when you say ignore further errors, you miss out on any new errors that might have information on what is wrong on their dialog.

We need information of what the error is in the log, not just that one occurred!  Sometimes, even the record involved is missing.  In that case the log entry is about as useful as the proverbial "mamaries on a bull".

Reported,
Paolo

[Uffe]

+ a couple thousand.

If in doubt, dump everything in the log. There's an option to disable it completely, which provides about the same level of fault-finding information as the current log does, so travellers with Seat-of-the-Pants Airways can always choose to switch it off.

(Oh, and: "ignore future errors" should have no bearing on what goes in the log. But that's obvious, right?)

/Uffe

[Paolo F Cantoni]

+ a couple thousand.

If in doubt, dump everything in the log. There's an option to disable it completely, which provides about the same level of fault-finding information as the current log does, so travellers with Seat-of-the-Pants Airways can always choose to switch it off.

(Oh, and: "ignore future errors" should have no bearing on what goes in the log. But that's obvious, right?)

/Uffe

As we've discussed before, Francis Urquhart's "You might well think that; I couldn't possibly say that." applies.

Paolo

[qwerty]

What about general SQL, XMI import, MDG activation and Project Integrity (checking) errors? Should there be a general log file (with configurable verbosity) at a dedicated place?

q.

[Uffe]

As we've discussed before, Francis Urquhart's "You might well think that; I couldn't possibly say that." applies.

As, indeed, does Nicola Murray's "You might comment; I couldn't possibly say 'yes'."

What about general SQL, XMI import, MDG activation and Project Integrity (checking) errors? Should there be a general log file (with configurable verbosity) at a dedicated place?

That would be good, and the dedicated place is the Windows log, not an EA-specific log file (why-oh-why does it seem to be so hard for software developers these days to actually use the infrastructure provided by the platform?). It would be very useful, but it's a bigger job.

/U

[qwerty]

These days? Hmm. You probably meant "ever since" :-(

q.