How do you create an Access 2007 project?

[BSman]

I have been using Access 2000 and 2003, mainly with Access front end applications connected to a SQL Server 2000 back end. I just purchased Access 2007 at home and am experimenting with it, both using my home business databases and to check some things out for my daytime job. Although I've searched through the typical Microsoft/Access help (looking for "create Access project", "create project" and the like), I can't find anything about how to create a new Access 2007 project, so I'd like to know how to do that.

Also, since I loaded the additions that come with Office 2007 that loaded SQL Server Express, I was thinking that I could possibly create a new Access project and use that to create a new SQL Express database, since my previous experience with Access project showed that I could do most things using project (and SQL Server 2000) that I could do with Enterprise manager. Is this possible?

Bob

 

[BSman]

I figured out how to create a new Access project in Access 2007....Once again, Microsoft has created a more difficult, crappy interface. Here's what you have to do to create an Access project, even though, based on the options you see when you select "new" in Access you would not even realize that you could create an Access project:

1. You must select the open folder picture next to the name you want for the new database.

2. In the dialog box, in addition to selecting the specific folder where you want your new database to be located, there is at the bottom a drop down box that has Access project as one of its selections. If you pick Access project the extension will change and you can create an Access project.

Actually, I found this by accident. Microsoft makes life more difficult with this kind of nonsense.

Bob

 

[BillKuhn]

Be warned - Microsoft has 'deprecated' ADP projects in Access 2007. That is a politically correct way of saying they are buggy as an anthill in 2007.

I went through a nightmare conversion of an Access2003 MDP to an Access2007 ADP (using SQL 2005). Incredibly painful finding workarounds to broken and/or missing features.

Personally I write off Access 2007 if you need to work with SQL data. Use another environment.

Bill Kuhn - MCSE
bkuhn@kuhngroup.com
The Kuhn Group, Inc.

http://www.kuhngroup.com

 

[BSman]

I think that any conversion of an MDB to an ADP can be a nightmare, whether you are talking Access 2003 or 2007. In fact, I'm not sure why you would even bother. Project is useful for some things, but I find it to be much slower (in Access 2003) for things like entering data (typing text in a memo field, for example). My main use at this point is to help in support of SQL Server 2000 databases (of which we have many in-house systems using that), since the 2005 enterprise manager cannot deal with relationship diagrams in a 2000 SQL Server database. However, Access project lets you create and manage relationship diagrams very easily.

Why not use Access 2007 as the application front end for a SQL Server database? It certainly works well in 2003 (through ODBC) and should be similar in 2007. But I wouldn't use Access project.

Bob

 

[Darrylles]

BSman,

I've recently posted a new thread, and you seem to have experienced the pain already.

Could you visit this thread and possibly reply to it?

thread958-1528961

In any case, when you say use Access as the front-end and connect to SQL Server back-end via ODBC - is this still a true client-server connection method?
Would this connection method pay dividends in performance improvement over JET under any circumstances?

Any help appreciated.

ATB

Darrylle


Never argue with an idiot, he'll bring you down to his level - then beat you with experience.