Access / DAO - What's the Future
- From: "TrevorS" <tstokes@xxxxxxxxxx>
- Date: 22 Sep 2006 08:08:00 -0700
We are using Access as the "repository" for a C++ MFC application. It's
single user.
The schema is complex (100 tables) and can be a few hundred MBytes in
size.
We are starting to reach the limits: occassionl "Query too Complex" and
"Max Lock Files Exceeded". Although some of these we have tackled and
got around through better design.
We recently moved to Visual Studio 2005 and of course no longer have
the benifit of DAO wizards for creating RecordSets and refreshing them
when the schema changes. This too we have got around for now - just
using old classes as a model and creating them by hand.
We are about to start the next phase of our product and it will stress
the database even more.
The questions:
o Would you recommend that we change to SQL Server Express?
o What are our migration options? Do we have to convert everything to
ADO right away? I assume we can't use DAO with SQL Server. If we could
we migrate slowly - using ADO (or ODBC) for new classes.
o Or should we use ODBC?
Thanks
TrevorS.
.
- Follow-Ups:
- Re: Access / DAO - What's the Future
- From: Miha Markic [MVP C#]
- Re: Access / DAO - What's the Future
- Prev by Date: Re: Datagrid Problems
- Next by Date: BeginEdit is ignored
- Previous by thread: String[9]: the Size property has an invalid size of 0???
- Next by thread: Re: Access / DAO - What's the Future
- Index(es):
Relevant Pages
|