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-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.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
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar