Access 2003 Project (ADP) vs Access 2007 Project

[ions]

The following statement is made at http://www.databasedev.co.uk/access2007adp.html


"The process of creating an Access Project in Office 2007 is not as obvious as it was in the earlier versions. But you can still use those created in earlier versions as there are no file differences between versions."


I feel much more comfortable in Access 2003. Does the above statement mean that Access 2003 Project and Access 2007 Project are the same?

I want to develop in Access 2003 Project but the project requirement is for Access 2007 Project. Are they identical?

Thank you

 

[ions]

I found this interesting article

http://www.microsofttraining.net/article-320-new-features-microsoft-project-2007.html

 

[BobMcClellan]

Access2003 Projects will run fine under Access2007.

I develop using 2007 but save all .adp's as 2000.
Our users have either Access2k, Access2003 or Access2007.
I save in 2000 so regardless of what they are using, they can
open and use the .adp without issue.

The point is, if you prefer to develop in 2003, a user running 2007
should be able to open your .adp without issue.

hth,
..bob

 

[ions]

Bob,

Thank you for your input.

Is there some advantage to 2007 over 2003? For example can I make a nicer looking user interface (forms, reports) with 2007 ADP?

The reason I want to develop in Access 2003 is because I have it installed. I heard it's a nightmare to have both 2007 and 2003 installed on one machine. Using 2007 is going to force me to buy 2007 and a another machine to run it.

Thanks.

 

[BobMcClellan]

Ions,
I do not have 2007 & 2003 on the same machine. It definitely is a problem having them co-exist on the same machine. I like the user interface better in 2007. As far as the differences between the two go... I think the articles you referenced site the differences. I'm sure you can google for a comprehensive list. I pretty much live in SQL and like the RAD that Access provides. I started out having one machine loaded with 2003 and one with 2007 so that I could test everything developed in 2007 on the 2003 box. I moved the 2003 box to a different workstation quite some time ago and only have 2007 on my machine. My comfort level has been satisfied that I do not need to test on a 2003 box any longer. I know that If I save it in 2000 format... any version 2k forward will have no problem. Additionally, the front ends look the same but more polished as you go up in version. You should test for this to see what I mean. Save an .adp using 2007 but save in in 2002-2003 format. Open it in 2003 and then in 2007 and check out how the same forms look in each.

I know this reply was a bit winded.
hope it answers your question.
..bob

 

[ions]

Thanks Bob,

I will buy another machine for 2007.

Bob can you recommend a book on Access 2007 ADP? An Ebook is fine too.

Thanks.

 

[BobMcClellan]

I wish I could recommend a 2007 .adp book for you ions. I've been working with Access since 2.0 and was pretty comfortable working through the curve transitioning from 2003 to 2007.

I'm sure one of the other posters can recommend a good book.

If you are comfortable with developing in 2003, I do not believe that you will have too much of a problem with 2007. The ribbon takes a little getting used to but once you discover where every thing is, the layout makes sense.

good luck ions.

 

[ions]

Thanks Bob,

Peter.

 

[ions]

Does MS Access User Security (.mdw) work the same way in ADP as it does in MDB?

User Security I mean, privilages to open forms, edit data, read privilages etc...

No problem with MS Access 2003 ADP security being used in higher version Access 2007 ADP?

Thanks.

 

[ions]

Modified thread:

It may appear that ADP's don't work well with SQL Server 2005 and later.


Here is an interesting link to a discussion I had about ADPs on this forum.

http://www.access-programmers.co.uk/forums/showthread.php?t=179210

 

[BobMcClellan]

I just learned that ADP is no longer supported by MS. ADP technology doesn't work well with SQL Server 2005 and later.

MS Access Experts claim that ADP is a dead technology.

I hate to disagree with you but...
I use .adp across our wan with SQL2005 with no problems.
I think it works great. I do not use ODBC though. I use ADO
with stored procedures. I used it with SQL2000 and continue to
use it with 2005. If you are comfortable using SSMS to build your
stored procedures and create your tables, indexes, constraints and triggers then... you should have no problems.

 

[Banana]

ions,

I have to say that you are going to create confusion when you create several threads all over asking same question in different way or very closely related questions. I don't know if Bob has seen this thread that led you to this conclusion, but you basically started what? 5 new threads in a day? Not really good netiquette, I'm sorry to say.

Also, I would be careful with making broad-brush statements such as this:

MS Access Experts claim that ADP is a dead technology.

especially considering there is no formal "panel" of experts and I know of at least one other MVP who uses ADP. Yes, it's true to say ADP hasn't received any updates since 2002-ish, but I don't think it's as accurate to claim it's dead because it's still supported even in 2007. I will call it dead when I find one day that I can't create .adp in the next version but there's nothing stopping me from doing so in 2007.

 

[ions]

Banana if you would like I can delete the post that upset you.

Peter.

 

[Banana]

I understand that you're trying to be helpful, but the point was that you posted without any references or links the conclusion which you drew from another thread that not everybody may have had read.

No, don't bother deleting them. Just don't do it again.

 

[ions]

Bob,

Are you creating all your tables, Stored Procedures etc... using SSMS (not the Access UI)

Perhaps, that would explain why you are not getting errors described in the above mentioned thread when using SQL Server 2005

 

[BobMcClellan]

Bob,

Are you creating all your tables, Stored Procedures etc... using SSMS (not the Access UI)

Perhaps, that would explain why you are not getting errors described in the above mentioned thread when using SQL Server 2005

Ions,
Yes... I do everything in SSMS. The only thing I do in the Access UI is create the forms and code the ADO. It all works out well.
..sorry, I kind of jumped in late on this thread. Are you having problems building your apps? Are you trying to do everything in Access?

 

[ions]

Hi Bob,

Thanks for your response.

Yes the plan was to develop tables, views, stored procedures and functions using Access ADP UI. Based on feedback from the forum, ADP Query Grid and SQL Server 2005 and later don't mix.

I guess now it comes down to choosing between

1) .MDB (ACCDB) , pass through queries and ODBC links to SQL Server 2008

or

2) using ADP and designing all tables and queries using SSMS for SQL Server 2008.

Which option is more effecient? Which option is more scalable, easier to develop etc...

Thank you.

 

[Banana]

FWIW, I worked for clients with .MDB with SS 2000 and 2005 using both DAO and ADO but I find myself writing T-SQL in SSMS whenever I want a server-side processing (e.g. majority of the queries, especially for reporting) while using DAO saved queries for binding to the form (with some special cases of using ADO to utilize some T-SQL such as table-valued function and still having the updatability for form's bindings)

The principle is pretty same even when I was working for my old employer with MySQL as the backend, using mysql client & NaviCat to manage server-side logic & leaving only simple queries that are appropriate for form's recordsource.

 

[BobMcClellan]

Hello Ions,
>>
I guess now it comes down to choosing between
1) .MDB (ACCDB) , pass through queries and ODBC links to SQL Server 2008
<<
I can not offer an opinion on this option. I only have one app left still using an .mdb. I have been working a few nights a week to convert it to
an .adp with a SQL2005 back end. All other mission critical apps have been converted and are working fine. Again, I do not use ODBC at all.

>>
or
2) using ADP and designing all tables and queries using SSMS for SQL Server 2008.
Which option is more effecient? Which option is more scalable, easier to develop etc...
<<
I'm embarrassed to say but, I have not yet explored 2008 at all. I am still using 2005 for everything. That being said, using SSMS to design and build everything works very well for me in 2005. The forms go together quickly as you know... and then it's just a matter of using the stored procedures to do the work. I typically use the onCurrent event to return values to unbound controls via output params from a stored procedure. I build a class in access then execute the method that calls the sp. all values are stored to the class after the method executes and the values are returned very efficiently. If you are on a subform in datasheet view and hold the arrow key down to scroll through the list, you see the values on the main form changing instantly. There is no waiting for anything. I know this explanation was bit all over the place but I'm trying to cast my humble vote towards developing in SSMS and then using the RAD environment that Access offers to build your forms. It works well for me and is the way I have chosen to move forward with new projects.
hth,
..bob

 

[ions]

Hi Banana,

Thanks for your response.

You mention DAO... does this mean you had local tables as well as links to an MDB backend on top of ODBC links to SS 2005? The reason I ask this is because I was under the impression that SQL Server only works with ADO. (Please note I am new to SQL server development hence my numerous need for clarification)


I ordered the following book to learn more about Access Enterprise Application development.


Microsoft Access Projects with Microsoft SQL Server
Author: Ralf Albrecht (2002)

The only other book I found about Access Enterprise Application development is

Alison Balter's Mastering Access 2002 Enterprise Development.

Note both books were written in 2002.

Perhaps I need to buy a book on SSMS? Not quite sure what resources to read to learn about the latest Access Enterprise development and techniques. There are so many books about Access Desktop Application Development but not many about Access Client Server Development using SQL Server.


Thanks

Peter.