access as frontend to backend sql 2000

  • Thread starter Thread starter Cire
  • Start date Start date
C

Cire

Hello all,

i'm pretty new to access and sql, been reading up on them. currently i have
to develop a query system and using access as a frontend is one of my options.


my requirements are mainly speed, as the database and the users are based in
different countries.
ease of use with minimum coding involved and the ability to generate
spreadsheets(excel) from the results.

I understand that using pass through queries gives u results pretty quickly
but from what i read on other forums is that it doesnt support a graphical
user interface. knowledge of SQL statements is needed and my end-users have
very limited knowledge of them. are there any other functions of access that
would solve this?i'm worried that using linked tables will greatly mar
performance.

looking forward to your advice
Cheers
 
Dear Cire:

You can use either pass-thru queries, as from an MDB front end, or you may
use an ADP front end, already designed specifically for SQL Server
connectivity.

I would typically expect to connect to the database server over an internet
VPN facility. I have had excellent results with this. It is naturally not
as fast as being right on the LAN with the server, but it is very
reasonable, responding to each data request in seconds, not minutes. As
your connections are international, and none of my testing and experience
have been at any great distance (a few hundred miles) there may be some
sense in which my experience may not exactly apply, but if you have both
good bandwidth, and perhaps more important, good latency, it will work
reasonably well. These facilities of your connection can be tested before
you begin the project, so you can have reasonable expectations as to how the
finished product will act.

As to your statement regarding, "what i read on other forums is that it
doesnt support a graphical user interface" I would recommend that you place
the Access front end, which completely defines the graphic interface, on
each front end (client) computer. All that need be passed over the internet
is the data, which improves performance, and this certainly makes the GUI
available for every user. Only raw data need pass between the server and
client, and the client to server communications would be SQL commands, where
are generally shorter than the raw data.

This interface doesn't use "linked tables" at all, in the sense that Access
Jet operates. I've tried that over VPN as well, and for me it was a
disaster. No performance at all. The MSDE version of SQL Server that comes
with Access, expanded with the purchase of just one copy of Access Developer
Edition and one of SQL Server Developer Edition give you the tools for one
computer to be used as a development platform for all phases of the project,
along with licensing of what you need from Microsoft.

As I have had repeated good success with this arrangement, I recommend it
strongly for your consideration.

You may contact me by email for information on how I do this, or keep it
here in this newsgroup.

Tom Ellison
 
Wow...I've had exactly the same experiences you have, but you said that all
so much better than I could've. Good job, Tom!


Rob
 
Tom said:
Dear Cire:

You can use either pass-thru queries, as from an MDB front end, or you may
use an ADP front end, already designed specifically for SQL Server
connectivity.


Cire:
Dear Tom:

Thanks for your excellent and detailed response, it certainly cleared many of
my doubts. As for connecting to the database over VPN, could you explain this
more in detail? from my understanding, If I were to use a ADP frontend, the
normal connection from access to the SQL database would be OLE-DB since thats
the driver that my database uses, so VPN is another method from which my end
user's ADP frontend communicates with the database. And as u mentioned, its
possible to test the VPN connection, may i know how do i go about doing it? i
haven't use VPN much, in fact so far none at all, does it really pushes data
through a private network, isolating it from the main internet network?

This is a separate question: i have 6 end users who will use this tool, does
the pass-through query method works well when they are all, at the same time,
accessing the database through ADP? As i've heard access's concurrency isn't
very good. or does the fact that pass-through queries shifts the query
workload to the server itself and thus minimizing this problem?

looking forward to your response again.
Regards
Eric
 
Dear Eric:

Creating a VPN connection is not so difficult. Once done, the remote
machines function together just as though they were on a local network.

I'm sure there is a lot of software available to test a network and give you
statistics on its performance. Maybe pick one that includes something about
VPN testing, as the authors of such software would be more aware of what
goes well or poorly with VPN than I probably ever will.

For me, I've just been content to set up the VPN using tools standard to
Windows OS. Start / Settings / Network Connections / New Connection Wizard.

Set it up on both ends. In Windows Explorer, check that you can see the
remote machine on the LAN. Copy a file to it. Copy a large file to see
what bandwidth is. Copy a very small file to see what latency is like. Not
a terribly thorough test, but you can now set up the application just as you
would between a local server and client.

It creates a "tunnel" of encrypted communications. It's pretty secure as I
understand. I wouldn't necessarily use it for Top Secred military
information, but as I understand it there's a pretty high level of
encryption.

With what else can I help you?

Tom Ellison
 
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

Tom said:
[snip]

This interface doesn't use "linked tables" at all, in the sense that Access
Jet operates. I've tried that over VPN as well, and for me it was a
disaster. No performance at all. The MSDE version of SQL Server that comes
with Access, expanded with the purchase of just one copy of Access Developer
Edition and one of SQL Server Developer Edition give you the tools for one
computer to be used as a development platform for all phases of the project,
along with licensing of what you need from Microsoft.

As I have had repeated good success with this arrangement, I recommend it
strongly for your consideration.

You may contact me by email for information on how I do this, or keep it
here in this newsgroup.

Tom Ellison

[snip]
 
Al Williams:

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


Al Williams said:
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

Tom said:
[snip]

This interface doesn't use "linked tables" at all, in the sense that
Access Jet operates. I've tried that over VPN as well, and for me it was
a disaster. No performance at all. The MSDE version of SQL Server that
comes with Access, expanded with the purchase of just one copy of Access
Developer Edition and one of SQL Server Developer Edition give you the
tools for one computer to be used as a development platform for all
phases of the project, along with licensing of what you need from
Microsoft.

As I have had repeated good success with this arrangement, I recommend it
strongly for your consideration.

You may contact me by email for information on how I do this, or keep it
here in this newsgroup.

Tom Ellison

[snip]
 
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 said:
Al Williams:

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
[snip]
 
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 said:
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 said:
Al Williams:

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
[snip]
 
Tom,

Is ADE available as a standalone? I did a search on microsoft.com and
it appears that it is part of Visual Studio. Is there another way to
get it? Or is that what you meant by getting MSDN Universal - includes
ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom said:
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


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 said:
Al Williams:

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

[snip]
 
Dear Al:

You can buy ADE separately, but without Access it would do you little good.
I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft product,
and includes what is effectively "prepaid support." So, you'll be dealing
with Microsoft any way you go. (It's not cheap, so it's a major decision.
A bit under $2000 last I remember. It's all the same, so you may as well
shop for it. Support comes from MS no matter from whom you purchase.)
However, if you use 10% of what it comes with, you'll be light years ahead
on price. Also, it includes a download center for various older version of
products. If you distribute a product, you may need to test it against what
all recepients may have, so this will do you good.

Tom Ellison


Al Williams said:
Tom,

Is ADE available as a standalone? I did a search on microsoft.com and it
appears that it is part of Visual Studio. Is there another way to get it?
Or is that what you meant by getting MSDN Universal - includes ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom said:
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


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:

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


[snip]
 
Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere for
slightly less than the list price of $799 from Microsoft (I don't think
that I would need "team" versions). It just wasn't obvious to me that
it had to be part of Visual Studio and that it might be available either
standalone or in an even less expensive package which was the reason for
the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom said:
Dear Al:

You can buy ADE separately, but without Access it would do you little good.
I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft product,
and includes what is effectively "prepaid support." So, you'll be dealing
with Microsoft any way you go. (It's not cheap, so it's a major decision.
A bit under $2000 last I remember. It's all the same, so you may as well
shop for it. Support comes from MS no matter from whom you purchase.)
However, if you use 10% of what it comes with, you'll be light years ahead
on price. Also, it includes a download center for various older version of
products. If you distribute a product, you may need to test it against what
all recepients may have, so this will do you good.

Tom Ellison


Tom,

Is ADE available as a standalone? I did a search on microsoft.com and it
appears that it is part of Visual Studio. Is there another way to get it?
Or is that what you meant by getting MSDN Universal - includes ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom said:
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


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:

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


[snip]
 
Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase ADE
by itself and SQL Server Developer Edition. I don't think that's even half
the $799 put together.

Tom Ellison


Al Williams said:
Tom,

It appears to be bundled with Visual Studio. The least expensive approach
is Visual Studio Professional which is available elsewhere for slightly
less than the list price of $799 from Microsoft (I don't think that I
would need "team" versions). It just wasn't obvious to me that it had to
be part of Visual Studio and that it might be available either standalone
or in an even less expensive package which was the reason for the
question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom said:
Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So, you'll
be dealing with Microsoft any way you go. (It's not cheap, so it's a
major decision. A bit under $2000 last I remember. It's all the same, so
you may as well shop for it. Support comes from MS no matter from whom
you purchase.) However, if you use 10% of what it comes with, you'll be
light years ahead on price. Also, it includes a download center for
various older version of products. If you distribute a product, you may
need to test it against what all recepients may have, so this will do you
good.

Tom Ellison


Tom,

Is ADE available as a standalone? I did a search on microsoft.com and it
appears that it is part of Visual Studio. Is there another way to get
it? Or is that what you meant by getting MSDN Universal - includes ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:

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


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:

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


[snip]
 
Tom: Things changes a little since Access 2002.

You need to purchase the following in order to create an Access 2003 runtime
application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003 runtime
components and you have to have Access 2003 installed in order to install
the ADE.

If you're using MSDN, note that while VSTO is available in all subscription
levels of MSDN, the Access Developer Extensions are not included with all
versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

See http://msdn.microsoft.com/vstudio/office/officetools.aspx for more
details


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Tom Ellison said:
Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase ADE
by itself and SQL Server Developer Edition. I don't think that's even
half the $799 put together.

Tom Ellison


Al Williams said:
Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere for
slightly less than the list price of $799 from Microsoft (I don't think
that I would need "team" versions). It just wasn't obvious to me that it
had to be part of Visual Studio and that it might be available either
standalone or in an even less expensive package which was the reason for
the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom said:
Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So, you'll
be dealing with Microsoft any way you go. (It's not cheap, so it's a
major decision. A bit under $2000 last I remember. It's all the same,
so you may as well shop for it. Support comes from MS no matter from
whom you purchase.) However, if you use 10% of what it comes with,
you'll be light years ahead on price. Also, it includes a download
center for various older version of products. If you distribute a
product, you may need to test it against what all recepients may have,
so this will do you good.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message

Tom,

Is ADE available as a standalone? I did a search on microsoft.com and
it appears that it is part of Visual Studio. Is there another way to
get it? Or is that what you meant by getting MSDN Universal - includes
ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:

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


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:

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


[snip]
 
Dear Doug:

Yes, it does seem things have changed recently. I hadn't kept up with that.
My apologies to Al.

Al mentioned Visual Studio Pro. Is that what he needs now?

Tom Ellison


Douglas J. Steele said:
Tom: Things changes a little since Access 2002.

You need to purchase the following in order to create an Access 2003
runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003
runtime components and you have to have Access 2003 installed in order to
install the ADE.

If you're using MSDN, note that while VSTO is available in all
subscription levels of MSDN, the Access Developer Extensions are not
included with all versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

See http://msdn.microsoft.com/vstudio/office/officetools.aspx for more
details


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Tom Ellison said:
Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase
ADE by itself and SQL Server Developer Edition. I don't think that's
even half the $799 put together.

Tom Ellison


Al Williams said:
Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere for
slightly less than the list price of $799 from Microsoft (I don't think
that I would need "team" versions). It just wasn't obvious to me that
it had to be part of Visual Studio and that it might be available either
standalone or in an even less expensive package which was the reason for
the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom Ellison wrote:
Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So,
you'll be dealing with Microsoft any way you go. (It's not cheap, so
it's a major decision. A bit under $2000 last I remember. It's all the
same, so you may as well shop for it. Support comes from MS no matter
from whom you purchase.) However, if you use 10% of what it comes with,
you'll be light years ahead on price. Also, it includes a download
center for various older version of products. If you distribute a
product, you may need to test it against what all recepients may have,
so this will do you good.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message

Tom,

Is ADE available as a standalone? I did a search on microsoft.com and
it appears that it is part of Visual Studio. Is there another way to
get it? Or is that what you meant by getting MSDN Universal - includes
ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:

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


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:

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


[snip]
 
No, Tom. As I said, he needs Visual Studio Tools for Office (aka VSTO). It's
a different product.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Tom Ellison said:
Dear Doug:

Yes, it does seem things have changed recently. I hadn't kept up with
that. My apologies to Al.

Al mentioned Visual Studio Pro. Is that what he needs now?

Tom Ellison


Douglas J. Steele said:
Tom: Things changes a little since Access 2002.

You need to purchase the following in order to create an Access 2003
runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003
runtime components and you have to have Access 2003 installed in order to
install the ADE.

If you're using MSDN, note that while VSTO is available in all
subscription levels of MSDN, the Access Developer Extensions are not
included with all versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

See http://msdn.microsoft.com/vstudio/office/officetools.aspx for more
details


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Tom Ellison said:
Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase
ADE by itself and SQL Server Developer Edition. I don't think that's
even half the $799 put together.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message
Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere for
slightly less than the list price of $799 from Microsoft (I don't think
that I would need "team" versions). It just wasn't obvious to me that
it had to be part of Visual Studio and that it might be available
either standalone or in an even less expensive package which was the
reason for the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom Ellison wrote:
Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So,
you'll be dealing with Microsoft any way you go. (It's not cheap, so
it's a major decision. A bit under $2000 last I remember. It's all
the same, so you may as well shop for it. Support comes from MS no
matter from whom you purchase.) However, if you use 10% of what it
comes with, you'll be light years ahead on price. Also, it includes a
download center for various older version of products. If you
distribute a product, you may need to test it against what all
recepients may have, so this will do you good.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message

Tom,

Is ADE available as a standalone? I did a search on microsoft.com and
it appears that it is part of Visual Studio. Is there another way to
get it? Or is that what you meant by getting MSDN Universal - includes
ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:

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


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:

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


[snip]
 
Dear Doug:

I knew that's what you said, and recognized it is different from the Pro
version at which he said he was looking. I wanted to make sure we had it
clear that this was not the tool for the job, but that VSTO is the one, as
you have confirmed.

Thanks!

Tom Ellison


Douglas J. Steele said:
No, Tom. As I said, he needs Visual Studio Tools for Office (aka VSTO).
It's a different product.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Tom Ellison said:
Dear Doug:

Yes, it does seem things have changed recently. I hadn't kept up with
that. My apologies to Al.

Al mentioned Visual Studio Pro. Is that what he needs now?

Tom Ellison


Douglas J. Steele said:
Tom: Things changes a little since Access 2002.

You need to purchase the following in order to create an Access 2003
runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003
runtime components and you have to have Access 2003 installed in order
to install the ADE.

If you're using MSDN, note that while VSTO is available in all
subscription levels of MSDN, the Access Developer Extensions are not
included with all versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

See http://msdn.microsoft.com/vstudio/office/officetools.aspx for more
details


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase
ADE by itself and SQL Server Developer Edition. I don't think that's
even half the $799 put together.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message
Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere
for slightly less than the list price of $799 from Microsoft (I don't
think that I would need "team" versions). It just wasn't obvious to
me that it had to be part of Visual Studio and that it might be
available either standalone or in an even less expensive package which
was the reason for the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom Ellison wrote:
Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So,
you'll be dealing with Microsoft any way you go. (It's not cheap, so
it's a major decision. A bit under $2000 last I remember. It's all
the same, so you may as well shop for it. Support comes from MS no
matter from whom you purchase.) However, if you use 10% of what it
comes with, you'll be light years ahead on price. Also, it includes
a download center for various older version of products. If you
distribute a product, you may need to test it against what all
recepients may have, so this will do you good.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message

Tom,

Is ADE available as a standalone? I did a search on microsoft.com
and it appears that it is part of Visual Studio. Is there another
way to get it? Or is that what you meant by getting MSDN Universal -
includes ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:

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


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:

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


[snip]
 
Hi Doug,

Thank you for clarifying what is needed. I was looking at
http://msdn.microsoft.com/vstudio/products/subscriptions/chart/ which
appears to say that Professional is what is needed. But, after
receiving your input, I discovered that
http://msdn.microsoft.com/vstudio/products/compare/default.aspx says
that indeed VSTO is what I need. Thanks!

Al Williams


Tom said:
Dear Doug:

I knew that's what you said, and recognized it is different from the Pro
version at which he said he was looking. I wanted to make sure we had it
clear that this was not the tool for the job, but that VSTO is the one, as
you have confirmed.

Thanks!

Tom Ellison


No, Tom. As I said, he needs Visual Studio Tools for Office (aka VSTO).
It's a different product.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


Dear Doug:

Yes, it does seem things have changed recently. I hadn't kept up with
that. My apologies to Al.

Al mentioned Visual Studio Pro. Is that what he needs now?

Tom Ellison



Tom: Things changes a little since Access 2002.

You need to purchase the following in order to create an Access 2003
runtime application:

- Microsoft Access 2003
- Visual Studio Tools for Office 2003 (which includes the Access 2003
Developer Extensions)

The ADE is the product that gives you the license to deploy the 2003
runtime components and you have to have Access 2003 installed in order
to install the ADE.

If you're using MSDN, note that while VSTO is available in all
subscription levels of MSDN, the Access Developer Extensions are not
included with all versions. ADE is only available at Universal level.

The stand-alone VSTO box includes both VSTO and the ADE.

See http://msdn.microsoft.com/vstudio/office/officetools.aspx for more
details


--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)



Dear Al:

I'm glad to have been helpful.

Now, that ADE would be bundled with Visual Studio seems very peculiar.
Also, when I bought a copy of it, it didn't cost nearly $799 by itself.
Something seems wrong about this to me.

Do you already have Access? If so, then I recommend you just purchase
ADE by itself and SQL Server Developer Edition. I don't think that's
even half the $799 put together.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message

Tom,

It appears to be bundled with Visual Studio. The least expensive
approach is Visual Studio Professional which is available elsewhere
for slightly less than the list price of $799 from Microsoft (I don't
think that I would need "team" versions). It just wasn't obvious to
me that it had to be part of Visual Studio and that it might be
available either standalone or in an even less expensive package which
was the reason for the question.

Thank you very much for your answers; they've been a big help!

Al Williams


Tom Ellison wrote:

Dear Al:

You can buy ADE separately, but without Access it would do you little
good. I would call it an "add on" product.

I believe I've seen MSDN from other vendors, but it's a Microsoft
product, and includes what is effectively "prepaid support." So,
you'll be dealing with Microsoft any way you go. (It's not cheap, so
it's a major decision. A bit under $2000 last I remember. It's all
the same, so you may as well shop for it. Support comes from MS no
matter from whom you purchase.) However, if you use 10% of what it
comes with, you'll be light years ahead on price. Also, it includes
a download center for various older version of products. If you
distribute a product, you may need to test it against what all
recepients may have, so this will do you good.

Tom Ellison


"Al Williams" <"atwms AT aol DOT com"> wrote in message


Tom,

Is ADE available as a standalone? I did a search on microsoft.com
and it appears that it is part of Visual Studio. Is there another
way to get it? Or is that what you meant by getting MSDN Universal -
includes ADE?

Do you buy Universal through Microsoft or is it available elsewhere?

Thank you very much for your input.

Al William

Tom Ellison wrote:


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



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:

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


[snip]
 
Douglas,

I'm wondering which version of VSTO could (should?) be used. I have the
impression thas VSTO2003 would be OK, but the documentation I've read about
VSTO2005 doesn't mention Access at all.
Do you know whether VSTO2006 could be used to deploy Access2003?

Jan
 
I have to admit that I don't know. I just checked the VSTO 2005
documentation, and I agree, it doesn't mention Access. VSTO 2003 definitely
includes the Access 2003 run-time. AFAIK, there is no VSTO 2006.
 
Back
Top