I have access db1 (db1) that creates accessdb2 (db2). Db2 contains a table with a single record which contains various text, memo and date fields with information pertaining to the job and then puts the completed db2 in a field tech’s dropbox.
The fields in db2 are filled from various form fields (some of which may be null) before the db is
Copied to the dropbox.
From time-to-time (but not every time) the record in db2 ends up with #delete# fields and is therefore unusable. Not sure what causes this. Some googling seems to indicate it may have something to do with an autonumber id field in db2.
I understand the purpose of the app. You only have to make sure that the record in the stand-alone database has the necessary keys to link it back to the record it is supposed to update when the database
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.
Overview: This article:
(a) explains one principle method to cross-reference invoice items in Quickbooks®
(b) explores the reasons one might need to cross-reference invoice items
(c) provides a sample process for creating a M…
I see at least one EE question a week that pertains to using temporary tables in MS Access. But surprisingly, I was unable to find a single article devoted solely to this topic.
I don’t intend to describe all of the uses of temporary tables in t…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…