We run a database system that uses a visual basic front-end application (on Win XP pc's) with an Access database on a mapped drive on a server. There are about 5 concurrent users. It has been working happily for many years with the database being in Access 97 format.
Recently we updated the application and took the opportunity to convert the database to Access 2003. There were some necessary changes to the vb code to accommodate communication with the newer Access format.
The updated system works - but whenever we save a new record there is now a delay of about 20 - 40 seconds! Previously there was virtually no delay. Can you give us any clues as to why these awful delays may be occurring, and what we can do to avoid them? I don't think we can go back to Access 97!
Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat. The purpose of this eBook is to educate the reader about ransomware attacks.
The Visual Basic for Applications (VBA) language is at the heart of every application that you write. It is your key to taking Access beyond the world of wizards into a world where anything is possible. This article introduces you to…
With Microsoft Access, learn how to specify relationships between tables and set various options on the relationship.
Add the tables:
Create the relationship:
Decide if you’re going to set referential integrity:
Decide if you want cascade upda…