A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

converting an Access 2003 mdb to an adp



 
 
Thread Tools Display Modes
  #1  
Old October 29th, 2008, 08:45 PM posted to microsoft.public.access
Tom B.
external usenet poster
 
Posts: 21
Default converting an Access 2003 mdb to an adp

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?
  #2  
Old October 29th, 2008, 09:49 PM posted to microsoft.public.access
Norman Yuan[_4_]
external usenet poster
 
Posts: 51
Default converting an Access 2003 mdb to an adp

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." wrote in message
...
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?


  #3  
Old October 29th, 2008, 10:41 PM posted to microsoft.public.access
Tom B.
external usenet poster
 
Posts: 21
Default converting an Access 2003 mdb to an adp

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." wrote in message
...
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?



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:05 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.