MS Access Multiuser - RE: SQL Servers

Author

RE: SQL Servers

AccessToSQLUser

2006-02-13, 8:25 pm

Can you tell me if Access 2000 front end with SQL Server 2000 back end is a
viable\scalable solution to run a company accounting\quoting\i
nventory
software package. What would be it's limitations, advantages,
disadvantages? How many concurrent users?

Advantage to upgrade to 12 and SQL Server 2005?

We currently are converting 100 mb Access package to Access 2000 FE with SS
2000 BE. But are constantly having to justify that Access can handle it.
And constantly under pressure to switch to another FE like VB.net which would
be a large learning curve.

"Eric Butts [MSFT]" wrote:

> Hi,
>
> The SQL Server (or MSDE local server) you have permissions to.
>
> Remember the Database resides on SQL Server. ADP files are just front end
> applications (files) to the database.
>
> ADPs are NOT designed to be used as multi-user application like an MDB is
> used.
>
> I hope this helps! If you have additional questions on this topic, please
> respond back to this posting.
>
>
> Regards,
>
> Eric Butts
> Microsoft Access Support
> ebutts@online.microsoft.com
> "Microsoft Security Announcement: Have you installed the patch for
> Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
> you to review the information at the following link regarding Microsoft
> Security Bulletin MS03-026
> <http://www.microsoft.com/security/s...ns/ms03-026.asp> and/or
> to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
> the patch. Running the SCAN program from the Windows Update site will help
> to insure you are current with all security patches, not just MS03-026."
>
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
> --------------------
> | Thread-Topic: SQL Servers
> | thread-index: AcR/ tWrmmcqUmYHST+2MtZHm
pyBNDw==
> | X-WBNR-Posting-Host: 192.158.55.16
> | From: "=?Utf-8?B?YnVyZw==?=" <burg@discussions.microsoft.com>
> | Subject: SQL Servers
> | Date: Wed, 11 Aug 2004 08:11:03 -0700
> | Lines: 2
> | Message-ID: <1CD66846-B700-49F0-98A9- 8445BFB4B22C@microso
ft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.access.multiuser
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.access.multiuser:38696
> | X-Tomcat-NG: microsoft.public.access.multiuser
> |
> | What sql server should i choose form the list when it open the wizard
> when i
> | start a new project? Are projects good for multi users?
> |
>
>

Tony Toews

2006-02-14, 1:24 pm

AccessToSQLUser < AccessToSQLUser@disc
ussions.microsoft.com> wrote:

>Can you tell me if Access 2000 front end with SQL Server 2000 back end is a
>viable\scalable solution to run a company accounting\quoting\i
nventory
>software package. What would be it's limitations, advantages,
>disadvantages? How many concurrent users?

How many users can hit SQL Server 2000? Thousands if it's scaled up
properly.

There are quite a number of Access applications out there happily
running against SQL Server. I suspect most of the apps at the
Microsoft Access Accounting Systems page at
http://www.granite.ab.ca/accsacct.htm

>Advantage to upgrade to 12 and SQL Server 2005?

Certainly not yet. And likely not for a while. After all Access has
two main uses. One is by the end user to build simplish databases or
do data querying. The other is by the developer to build solutions.
Which is you situation. That usage means you have folks who are
using your app to do their job, such as accounting. What do they care
what version of Access you are using or something else such as Cobol
or Fortran?

Now once Access 12 is available you may want to move to it for
development purposes as your developers will likely become more
productive. But there's nothing stopping you from, for example,
distributing your app in A2000 because the runtime will install on
Windows 98 systems. (At least I'm pretty sure it will. I've
momentarily forgotten.)

>We currently are converting 100 mb Access package to Access 2000 FE with SS
>2000 BE. But are constantly having to justify that Access can handle it.
>And constantly under pressure to switch to another FE like VB.net which would
>be a large learning curve.

The most important part in that equation is the cost of software
development. SQL Server is an excellent choice in appropriate
environments.

But converting your app to VB will take months and months if not
years. And for what? Estimates from folks experienced in both Access
and VB are that it will take from 50% to 100% longer to develop the
same Access in VB.

One person estimates six times as longer to do the same app in VB.Net.
Now that person may have been exaggerating a bit.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Sponsored Links