Upsizing to SQL Server backend

[Bill Reed via AccessMonster.com]

I read a rather long discussion in this ng about Access/SQL Server issues. Is
there a consensus as to the best way to implement an SQL Server BE in Access?
Should I go with .adp for a front end, or .mdb and DAO, or .mdb and ADODB? I
have the virtue of being equally ignorant in all 3 disciplines.

Thanks

 

[Sylvain Lafontaine]

Even the longest voyages begin with a first step: so, if you have the virtue
of being ignorant, you should begin with MDB and DAO. Later, if (when) the
forms are too slow, starts adding Views here and there. See
http://support.microsoft.com/kb/q209123/ for having updatable views.

Unless you have strong requirements about security or the
size/complexity/LAN/WAN of the database, forget about ADP; as they are now
the living deads at MS.

I don't know what you mean by MDB with ADODB but if you are talking about
using unbound forms inside MDB, then you should keep this for later, when
you will have lose your virtue.

If you have a powerfull machine, then your other possibility would be to
take a look at the .NET Framework Beta 2.

Don't wonder if someone else chime in and told you that the next version of
Access will be so powerfull for developers that it will become the equal (or
even the replacement) of .NET. Other people (like me for example) thinks
that this is only a bone that MS will throw at Access' developers to gnawl
on until Longhorn is finished; which will give MS the opportunity to free
the necessary internal resources to fully port MS-Office to the .NET
Framework.

Also, don't forget that other technologies relying on classic Visual Basic
and ADO - like VB6, ASP and DTS 2000 - have already been dumped by MS. If
you plan to use something like ASP.NET for your web site, then you will feel
more at home if you start with VS2003 or VS2005 from the beginning than with
Access MDB.

 

[Bill R via AccessMonster.com]

I was just reviewing my posts in case I had neglected to thank anyone. I will
be going with .mdb and DAO.

THANK YOU!!

Bill

Even the longest voyages begin with a first step: so, if you have the virtue
of being ignorant, you should begin with MDB and DAO. Later, if (when) the
forms are too slow, starts adding Views here and there. See
http://support.microsoft.com/kb/q209123/ for having updatable views.

Unless you have strong requirements about security or the
size/complexity/LAN/WAN of the database, forget about ADP; as they are now
the living deads at MS.

I don't know what you mean by MDB with ADODB but if you are talking about
using unbound forms inside MDB, then you should keep this for later, when
you will have lose your virtue.

If you have a powerfull machine, then your other possibility would be to
take a look at the .NET Framework Beta 2.

Don't wonder if someone else chime in and told you that the next version of
Access will be so powerfull for developers that it will become the equal (or
even the replacement) of .NET. Other people (like me for example) thinks
that this is only a bone that MS will throw at Access' developers to gnawl
on until Longhorn is finished; which will give MS the opportunity to free
the necessary internal resources to fully port MS-Office to the .NET
Framework.

Also, don't forget that other technologies relying on classic Visual Basic
and ADO - like VB6, ASP and DTS 2000 - have already been dumped by MS. If
you plan to use something like ASP.NET for your web site, then you will feel
more at home if you start with VS2003 or VS2005 from the beginning than with
Access MDB.

I read a rather long discussion in this ng about Access/SQL Server issues.
Is

[quoted text clipped - 5 lines]

Thanks