Re: How do I use Access 2003 with SQL Server Express?


The original question was, as I understood it, about designing a SQL Server
2005 database using Access 2003. This question seems to be about which tool
to use to build a front-end application, which is a very different
discussion.

Generally speaking, for designing data-centric desktop applications, I think
Access still has the edge. It's true that if you use unbound forms you will
give up many of the advantages of using Access (so make sure you have a
really good reason for doing so) but even so you'll still probably have to
write considerably less code in Access than you would in .NET. If you're
developing a Web application, then of course you should use a tool designed
for developing Web applications.

In Access, you're only choice for Web applications is Data Access Pages.
These are now deprecated in Access 2007 (you can run existing DAPs, but can
not make design changes to them or create new ones in Access 2007). So I
certainly would not recommend Access for developing Web applications. For
Web applications, ASP.NET is a great choice - provided, of course, that you
don't work for an organisation that has standardised on UNIX and JSP!

This of course begs the question of when to use a Web application and when
to use a desktop application, but perhaps that's a discussion for another
day! :-)

--
Brendan Reynolds
Access MVP

<John F> wrote in message
news:0A732B7E-7AAB-4126-8364-62B2D3F80B09@xxxxxxxxxxxxxxxx
Thanks Brendan,

I guess my major options are to 1) use Access 2003 with SQL Server 2000 or
an MSDE version, or 2) Drop Access 2003 and use instead Visual Studio
either
Express or full version.

I have the impression that if I want the control of using unbound controls
on forms, then I have to code anyway and there does not seem to be any
major
advantage in using Access 2003 over Visual Studio and coding in VB.NET or
C#.
Do you agree?

Thanks,

John


"Brendan Reynolds" wrote:

There is no update that adds design support for SQL Server 2005 to Access
2003.

--
Brendan Reynolds
Access MVP

<John F> wrote in message
news:0C8AB120-0752-4BA2-9B3D-14D59C533A6C@xxxxxxxxxxxxxxxx
In response to the original post, I found that just using the instance
name
gives the error message noted. The machine name followed by instance
connected ok - e.g machinename\SQLEXPRESS.

My question-

Using upsizine wizard to work with SSE 2005, all seemed ok, but I get
two
messages 1) when opening a table in Design Mode, message

This version does not support design changes with the version of SQL
Server
your access project is connected to. See the Office Update Web site
for
latest info on downloads. Your design changes will not be changed.

Then another window

You have connected to a version of SQL Server later than SQL Server
2000.
... you might encounter problems. Pls check to see if there is a
Service
Pack that you should apply to Visual Studio or Office....

I did not see any download that appeared obvious for this. Any help?

Thanks.

John






.

Relevant Pages

  • Re: How to handle concurrency issue with better performance?
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... Then for timestamp, it will be unique? ... Collisions occur because your design permits ... select command). ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: How do I use Access 2003 with SQL Server Express?
    ... There is no update that adds design support for SQL Server 2005 to Access ... This version does not support design changes with the version of SQL ...
    (microsoft.public.access.setupconfig)
  • Re: ORDER BY in VIEW not working
    ... As an object-oriented programmer, I expect to be able to encapsulate ... The relevant design principle is that of Orthogonal Design. ... State what version of SQL Server you are using and specify the content ...
    (comp.databases.ms-sqlserver)
  • Re: Target number of database reads per user
    ... Yeah, just to echo what Andy is saying, if you want to have the question ... If you can post code/database design we could all take a look. ... Pro SQL Server 2000 Database Design - ...
    (microsoft.public.sqlserver.programming)
  • Re: Access Form connected to SQL table in Access Data Project (.adp file)
    ... Under the previous design, he would just open the form and could ... navigate through the last few orders by clicking "next record" a few times. ... > the form what records it should load. ... we are NOT even using sql server yet. ...
    (microsoft.public.access.conversion)
Loading