No warning given

[Sprocket]

I have an A2K database on a shared drive - usually with 8 to 10 concurrent users.
Recently we have experienced some network difficulties whereby we temporarily loose contact with the server.

This is NOT a problem related to Access but to a Netware system upgrade.

However, the first you know about this is when you try move to a new record and the record does not update.

Disconcertingly, if you don't move to a new record but close the current form/record and return to the opening switchboard screen you are not made aware of a network problem at all ---

The first you know about this is when you go bact to the record you were in at the time link was lost and you discover changes you made to the record have not been saved.

I have always been under the impression that when you exit a record it automatically saves the changes. I would have expected therefore that Access would have given a generic warning that it could not update the record, but this has not been happening.

Is there a simple way to ensure that you get an understandable warning should this occur in future.

Many thanks....Sprocket

PS because of the low number of users the whole database is sat on the shared drive - it is not split to Front-end / Back-end. Maybe this makes a difference!!

 

[Fizzio]

I would split this into a FE / BE regardless of the number of users as this will

a) give you a performance boost
b) allow you to trap for a broken connection.

I have posted somewhere here a check links module. (If I find it before you I'll point you in the right direction)

As you seem to lose connection regularly, I would be tempted to check the links after an update - mind you, if you lose the connection, access will tell you when you are trying to update a record but with the check_links code, you can present a more 'user friendly' message to your concurrent users.

 

[Sprocket]

Fizzio -- I have found your "Checklinks" code and will give it a try.

I have avoided the FE/BE split up to now as it seems rather daunting..... but I suppose we all have to grow up and fly the nest some time.


Many thanks......Sprocket

 

[Mile-O]

I have avoided the FE/BE split up to now as it seems rather daunting.....

Daunting? Just go to Tools -> Database Splitter and let the wizard do it for you.

 

[Sprocket]

I don't like wizards... they do things that can't be easily undone. I tried splitting a database in Access 97 using the wizard and it totally trashed my database. Happily I had a backup and I've stuck with the solid model ever since. But A2K may be better so I'll give it another go.