Behaviour under unexpected file/dbms problems

[Stringer]

Today I experienced it. My WLAN network disconnected itself for good while I was modeling a diagram, or more like when I had to exit the program with unsaved diagram.

The program tried to connect serveral times to the server (probably in different functions) and every time the OLEDB driver tried to ask a password. Then after few times it said that it was unable to save and that it would try to re-open the diagram from server. That made it to try serveral more connections before it finally crashed the program.

Now here is what it should have made in the situation: ask user if it is OK to quit without saving after 1-3 tries to re-connect.

[«Midnight»]

Please report this one to Sparx directly.

I think you know the drill.

David