Visual Database Tools for SQL 2008

[Dredy]

Hi,

does anybody know if there is a Visual Database Tools update in order to
modify/edit objects when Access 2007 is connected to a SQL 2008 Server?

Office use the vdt70.dll instead the vdt80.dll installed by Visual Studio 2008


Many thanks i.a.

Dredy - Italy

 

[Tom van Stiphout]

On Fri, 9 Jan 2009 03:14:01 -0800, Dredy

Not that I know of. I have had no problems using A2007 with SQL2008.
For most management I find SSMS easier to use, and the intellisense
features are beginning to grow on me.

-Tom.
Microsoft Access MVP

 

[Dredy]

Hi Tom,

sorry, but You probably did not understood correctly my question:
are You able to edit objects (Tables, SP, Views, Functions) direct from
inside Access 2007 with a SQL 2008 backend?
I'm wondering on how it works. . .
My Access 2007 states that is unable to edit object because the version of
SQL.

When attached to a SQL 2005 machine it works fine, obviously.
Same issue that I've found when Access 2003 has a SQL 2005 backend: it
cannot edit objects that is on a SQL version newer than SQL 2000.

I do NOT find SSMS easier to use.
For me (15 years using msAccess, 10 Years using ADP files and SQL as
back-end) is more "familiar" the msAccess way... I do use Access ADP files as
a front-end for editing and manage SQL databases that are on a web server.
The VS integrated editor is "ridicolous" and SSMS is not user friendly (this
is my point of view ...)

Anyway: for now i MUST use SSMS (no other way ...) but i'm not happy of this.

My question was on "is microsoft working on a solution?" or the problem is:
no way!

Regards,

Dredy - Italy

 

[Tom van Stiphout]

On Fri, 9 Jan 2009 06:14:01 -0800, Dredy

Ah, got you. No, I cannot. I can change data, but not objects.
I'm not aware of MSFT working on a solution for A2007. If memory
serves in previous cases where this happened we had to wait for a new
version of Access to get the desired support.

-Tom.
Microsoft Access MVP

 

[Dredy]

Yes, i agree with Your "reading of the situation"... Memory serves ...
Honestly, i hope that MS is working on a solution. The next version of
Office is for 2010 ...

Bye