Re: access as frontend to backend sql 2000
- From: "Tom Ellison" <tellison@xxxxxxxxxxx>
- Date: Fri, 10 Feb 2006 20:28:38 -0600
Dear Al:
To be technically correct, ADE is an "add on" to Access. You obviously must
have that, too. With that, I've found I don't need anything else. I do use
FMS Enterprise Suite as well. It's not what I'd call an essential for me,
but it has a positive role. As far as what to buy, a good selection is MSDN
Universal. That gives you (and only you) access to the whole set of
Microsoft development tools, licensed for several computers. You can set up
an "imitation" of the entire deployment you plan, with different OS
platforms and different versions of other software. Testing deployment can
be a major part of a complete project. The project isn't complete until
it's deployed. For an initial deployment this is important, but for an
upgraded deployment it is critical. When users are counting on a system
they have been using for some time, and you're replacing that with a newer
version, having it fail is more critical than having teething trouble with a
brand new deployment that no one is counting on daily.
SQL Server Express may be just the thing for you. Good choice. And, if it
gets too small, you have an easy (though not necessarily inexpensive)
upgrade path. You might also look at Windows Small Business Server bundled
with SQL Server. That's an effective "medium scale" setup with OS and
database combined. It's less expensive initially and less expensive for
adding licenses. That's for the production side once the project's done,
but if you're going to have to buy it for production, you may as well have
it in advance for testing and for deployment preparations.
Just what you should do depends on the size of the deployment, the
availablility of funds, and your progress along that learning curve. If you
need help, just let me know!
Tom Ellison
"Al Williams" <"atwms AT aol DOT com"> wrote in message
news:OGZsGuqLGHA.2416@xxxxxxxxxxxxxxxxxxxxxxx
Tom,
Some background: I have an backend mdb that contains just over 560MB.
Since it continues to grow as new features are added and even more data is
inserted, I've started to think about going to something that has more
capacity. I understand that a backend's max capacity is 2GB and that
MSDE's is also. So I was thinking about going to SQL Server 2005 Express
(4GB) with both Access 2002 and Access 2003 being used by the users for
frontends.
As I've been following some of the newsgroup comments, I've found the
options/suggestions confusing. I'd like to expand my question. Do you
find that you need other tools besides ADE and SQL DE for such an
environment?
I should mention that this is my first database and I just happened to do
one that has become very popular with this organization. So, I'm on a
steep learning curve to keep up with it. Hence my desire to get some good
input. Thanks.
Al Williams
Tom Ellison wrote:
Al Williams:[snip]
Access Developer Edition (ADE) includes a license to distribute MSDE and
Access run-time applications to clients without any special license. It
includes tools to create run-time.
SQL Server Developer Edition (SQL DE) includess development tools,
especially Enterprise Manager and Query Analyzer (EM and QA) that are
indispensable. "Don't leave home without it!" (TM) class of benefits!
Improves productivity working with MSDE, and online help you cannot get
along without.
Wow! That endorsement reads like some kind of commercial.
If you don't need distribution to clients without Access installed, then
ADE is optional. If you are going to develop MSDE applications SQL DE is
not optional. It is very inexpensive. It pays for itself in less than a
week.
Tom Ellison
[snip]
Hi Tom,
I would appreciate an explanation of how you use Access Developer Edition
and SQL Server Developer Edition. Will your approach work with SQL
Server 2005 Express? Thanks.
Al Williams
.
- Follow-Ups:
- Re: access as frontend to backend sql 2000
- From: Al Williams
- Re: access as frontend to backend sql 2000
- References:
- access as frontend to backend sql 2000
- From: Cire
- Re: access as frontend to backend sql 2000
- From: Tom Ellison
- Re: access as frontend to backend sql 2000
- From: Al Williams
- Re: access as frontend to backend sql 2000
- From: Tom Ellison
- Re: access as frontend to backend sql 2000
- From: Al Williams
- access as frontend to backend sql 2000
- Prev by Date: Re: access as frontend to backend sql 2000
- Next by Date: Re: access as frontend to backend sql 2000
- Previous by thread: Re: access as frontend to backend sql 2000
- Next by thread: Re: access as frontend to backend sql 2000
- Index(es):
Relevant Pages
|
Loading
