Thanks for the info. Bill.
You've convinced me, I just need to convince the others here now.
Cheers,
Stuart
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
Sent: Friday, 9 August 2013 4:46 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: Using Access as frontend to Firebird or SQL
Server Backend
>What size databases and how many users do your applications support?
I have various sizes ranging from 100 Mg to some over 5 Gb.
A couple of my biggest ones support 100+ concurrent users.
>This will be used as an internal network program so I can't really see any
>downside to using Access for this purpose.
As long as each user has his own front end and you control the security at
the
SQL Server end Access will work just fine.
>I can see lots of pluses but are there any situations where Access as
>frontend would not be appropriate?
I work for a hospital and some of my apps contain protected health
information
(PHI) which means I have to comply with HIPAA regulations. As long as the
data
is protected in SQL Server and you set up permissions correctly you won't
have
any problems. One of the things I do is to use Windows Authentication on my
SQL
databases. Even if someone should get into the Access application he
couldn't
see the data unless he was authorized in the back end.
>I'm currently using Access 2007, would you (or anyone) say it is worth it
to
>upgrade to 2010 or 2013 yet? Are they more stable than 2007?
I hated 2007, but I love 2010. So far I haven't seen a need to move up to
2013.
Maybe if MS ever gets the web stuff working better I will upgrade.
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Stuart
Luckman
Sent: Wednesday, August 07, 2013 6:03 PM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: RE: [MS_AccessPros] Re: Using Access as frontend to Firebird or SQL
Server Backend
Bill,
Thanks for the great article link.
I'm already pretty set on using SQL server, I was more concerned about any
limitations with using Access Runtime as a front end.
As usual with managers they have been told that Access is an inferior
product to C#, VB, Delphi, Java etc. and are wondering why I would pursue
this as an option, so I need a bit of ammo to support using it.
What size databases and how many users do your applications support?
This will be used as an internal network program so I can't really see any
downside to using Access for this purpose.
I can see lots of pluses but are there any situations where Access as
frontend would not be appropriate?
I'm currently using Access 2007, would you (or anyone) say it is worth it to
upgrade to 2010 or 2013 yet? Are they more stable than 2007?
Thanks,
Stuart
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Bill Mosca
Sent: Wednesday, 7 August 2013 12:17 AM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: [MS_AccessPros] Re: Using Access as frontend to Firebird or SQL
Server Backend
Stu
Welcome to our group! I haven't worked with Firebird, but SQL Server is
definitely a perfect choice for a back end. That's what I use for all my
Access applications.
Be sure every table has a primary key and a timestamp column. Also make sure
every bit (Yes/No) column has a default value and cannot be null.
For more info on using SQL Server with Access see my article "Working with
SQL Server Linked Tables: The Hidden Gotchas" at
http://www.thatlldoit.com/Pages/howtosarticles.aspx
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-6427073088
1E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com>
<mailto:MS_Access_Professionals%40yahoogroups.com> , "discostubacca"
<stuluck22@...> wrote:
>
> Hi all,
>
> I was just wondering about any limitations to using Access as a frontend
to Firebird or SQL Server (express maybe) backend.
> I think the boss wants me to learn VB or C# or Delphi but I was hoping
that Access would still be suitable.
> Database is about 2.6 GB, in Firebird currently, growing at about
600MB/Year.
> On a Windows 2003 Server.
> There would be about 70 or 80 users.
> It will be a Production/Inventory/Sales program so a lot of users on 12hrs
a day.
> I was thinking of just using pass through queries and stored procedure
calls so processing would be done by the server.
> Am I right in saying that as long as every user has their own copy on
their workstation then there wouldn't be a limit really to using Access as
frontend?
>
> Thanks,
> Stu
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (5) |
Tidak ada komentar:
Posting Komentar