I currently have an Access 2003 database with about 15 users and I'm
interested in converting it to an adp. Should I use the SQL Server 2000
engine, or would I be better off going to SQL Server 2005 Express Edition, or
even the 2008 Express Edition?

I hope the motif to the conversion is not just because there is 15 or 30
users. Mereky that number of users hardly causes issues with well designed
Access application.

With that said, converting back end to SQL Server could be a good move while
converting FE to ADP could likely be a bad one, considering:

1. ADP is on its way out. Access2007 could be the last Access version
supporting ADP. MS Access team recommeds using *.mdb or *.accdb FE instead
of ADP FE in most cases.
2. If you use SQL Server2005/8/Express, you cannot use Access2003 to design
SQL Server objects (table, view, SPs, UDF...). To do serverside object
design with Access, you need Access2007 (but I am not should if it work with
SQL Server2008, I'll bet it is no).

Of course you still can go with ADP if it is the best choice to your
situation, such as you use ADP mainly as SQL Server's reporting tool, it is
still pretty good tool.

"Tom B." <(E-Mail Removed)> wrote in message
news:55B1831E-40DC-418B-9F19-(E-Mail Removed)...
>I currently have an Access 2003 database with about 15 users and I'm
> interested in converting it to an adp. Should I use the SQL Server 2000
> engine, or would I be better off going to SQL Server 2005 Express Edition,
> or
> even the 2008 Express Edition?

Thanks, Norman. You gave me a lot of good info.

"Norman Yuan" wrote:

> I hope the motif to the conversion is not just because there is 15 or 30
> users. Mereky that number of users hardly causes issues with well designed
> Access application.
>
> With that said, converting back end to SQL Server could be a good move while
> converting FE to ADP could likely be a bad one, considering:
>
> 1. ADP is on its way out. Access2007 could be the last Access version
> supporting ADP. MS Access team recommeds using *.mdb or *.accdb FE instead
> of ADP FE in most cases.
> 2. If you use SQL Server2005/8/Express, you cannot use Access2003 to design
> SQL Server objects (table, view, SPs, UDF...). To do serverside object
> design with Access, you need Access2007 (but I am not should if it work with
> SQL Server2008, I'll bet it is no).
>
> Of course you still can go with ADP if it is the best choice to your
> situation, such as you use ADP mainly as SQL Server's reporting tool, it is
> still pretty good tool.
>
> "Tom B." <(E-Mail Removed)> wrote in message
> news:55B1831E-40DC-418B-9F19-(E-Mail Removed)...
> >I currently have an Access 2003 database with about 15 users and I'm
> > interested in converting it to an adp. Should I use the SQL Server 2000
> > engine, or would I be better off going to SQL Server 2005 Express Edition,
> > or
> > even the 2008 Express Edition?
>
>