I don't see that local Access tables vs. Class Modules as being mutually exclusive; one is about data handling, the other about how you code. Class Modules are supposedly, theoretically, a "better" way to code, for reasons I don't want to debate, save that if you want to learn other OO languages, it is a good conceptual start.
The question here should be Local Access temp tables vs. MSSQL temp tables; I 've done both, your choice should come down to performance and maintainability. In one case, I had MSSQL do in seconds what took Access hours; stored procedures are your friend. Real MSSQL temp tables disappear after the SP that created them runs, so clean-up is not needed. I actually however persist "temp" tables on MSSQL in some cases, and just empty them, but leave the structure in place when the reporting process is done. This is all with on-premises MSSQL though and admittedly, I don't know yet the differences between on-premises and Azure MSSQL.
As always, your mileage may vary.
Steve Conklin
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Friday, August 1, 2014 4:58 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Re: Best option for handling data from Microsoft 365's Azure SQL
Ryan
I have rarely used class modules so I can't comment on whether or not you should use a class or a standard module. As to using local tables, it might be a good idea in this case. But beware that creating temp tables will bloat the front end. I'd set it to compact on close. While some think that risky it really isn't when it comes to a split database since if the FE blows up you just get a new copy.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
Microsoft Office Access MVP
My nothing-to-do-with-Access blog
Posted by: Stephen Conklin <stephenmconklin@hotmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
Tidak ada komentar:
Posting Komentar