Peter-
Yes, tabbed forms often imply multiple subforms - not a good idea if you're
trying to get good performance.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of jrweinwurm
Sent: Sunday, May 29, 2011 2:35 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] JET vs SQL Server Express
Thank you for the response John.
Would another recommendation be not to use Tabbed forms as I believe they all
load at once upon the Form's opening.
>> When implemented correctly, an all-Access solution can be easier to manage -
particularly if you're very comfortable with Access and have limited experience
with SQL Server.
Can you elaborate on this? Assume that comfort with either technology is not an
issue.
Thanks
Peter.
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> Peter-
>
> Any application that can stand to lose a day's worth of data isn't "mission
> critical" in my mind. Once you get over that hump, you have to decide which
> will be easier to manage. When implemented correctly, an all-Access solution
> can be easier to manage - particularly if you're very comfortable with Access
> and have limited experience with SQL Server. By correctly, I mean a true
> client/server setup with only the data shared on the back end and the app
> designed to minimize network traffic. Your app should never open a form or
> report unfiltered. And the filters you do apply should be supported with
> indexes. Avoid designing forms with multiple subforms. Don't build combo and
> list boxes that return more than 1000 rows.
>
> But having said all that, if this application is likely to grow over time, you
> will need to consider replacing the back end with SQL Server. That will be
easy
> to do if you've designed a good client/server app to begin with.
>
> I'm sure others will chime in... <s>
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of jrweinwurm
> Sent: Sunday, May 29, 2011 12:10 AM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] JET vs SQL Server Express
>
> Suppose you had a new client with a system request for 10 or less concurrent
> users with under 50 MB of data. The data was mission critical but losing a
> day's worth of data wouldn't be devastating.
>
> Would you ever recommend they go with .mdb / .accdb backend or do you
> automatically go with SQL Server Express?
>
> What are the advantages of sticking with .mdb / .accdb. I have yet to create
a
> multi-user system with an SQL Server backend and would like to hear your
> thoughts.
>
> Thank you
>
> Peter.
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
------------------------------------
Yahoo! Groups Links
Tidak ada komentar:
Posting Komentar