Modules VBA or Macros ?

[jamila]

Hello ,



im creating an MS Access database application, and i want to know the best method for creating actions and avoid bugs ..
Modules VBA OR Macros ?
NB : the application goes contains billions of records, actions : add, search, edit, print .
Thanks

[pbaldy]

You have more flexibility and power with VBA, and better error handling. Most experienced developers use VBA.

[Beetle]

...the application goes contains billions of records...
Thanks

Are you using Access as a front end for another database? Access can handle quite a few records, I have one app that has had up to +- 5 million rows before bumping up against the file size limit, I'm sure it could handle more with a few tweaks, but billions? Not with a Jet/Ace back end.

[jamila]

its an application database access its not just a front end for another database ,
yes billions of records , not with a Jet/Ace back end so what should i do ?

[isladogs]

How big is the file size?
Access has a 2GB size limit though you can get round that by splitting the database and putting the tables into one or more linked backend databases.
Using SQL Server for the BE gives a 10GB limit in the free Express edition and more in the paid versions.

However I'm also surprised by the 'billions' comment.
Is a billion a million millions (UK) or a thousand millions (USA)?

My largest Access backend db. is 1.6GB most of which is due to a single postcodes data table of 2.6 million records and around 40 fields.
I monitor is closely as if it ever reaches 2GB it will be unusable.

Anyway, what you need to do is make a backup then split your database

[Beetle]

I don't deal with data sets anywhere near that large, so I'm certainly no expert, but I'm having a hard time imaging any set of data containing billions of rows that would fit within the 2gb limit of Access, or even the 10gb limit of SQL Server Express. The full version of SQL Server maybe? Or you may be into Big Data territory where you're talking about something like Cassandra or HBase, but then you are completely outside of the realm of using Access at all I would think. Maybe I'm wrong.

Edit: Also, you can use multiple back ends to get around file size limits, I'm just wondering how many different back ends it would take to handle that much data. Doesn't sound like it would be practical.

[orange]

As others have said, I'm also suspicious of the billions of records. As my parents often said, "If I've told you once, I've told you a million times ---don't exaggerate.
My second thought is --if I had billions of records to store and maintain, would I even be considering Access?
But then I see this is your second post, so am more interested in you, your experience generally and database specifically, and most of all an overview of your proposed application that deals with billions of records.
So please tell us more in simple, plain English.

Your immediate decisions do not necessarily involve --vba vs macros.

Good luck.