• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

access DB design

bookman3

Junior Member
If you've heard of companies using MSAccess to store & manipulate flat files without any implementation of the relational db say Yes

if not, say no:


Anyone know how common it is for companies/individuals to use MSAccess to store and manipulate flat files, without any implementation of its relational db aspect?

The small analytical consulting company I work for receives data from multiple clients on a weekly basis (same files, structure differing between clients) and currently uses access this way to store & manipulate the tables using vba. Each client gets a db, no way to edit processes across all client dbs, no standard for variable names, queries, or modules
 
Last edited:
Yes, I have heard and seen it. Usually, I can convince them to setup a relational DB to prevent duplicate entries via typos.

If they choose to have a DB for each function/customer, that is their decision.
Most do not.
 
Back
Top