Disabled buttons on Access 2007 Ribbon

[Laury G Burr]

I'm developing an ADP project under Access 2007 (SP1, I believe) on Windows
XP2002 SP3. Most buttons on the "Database Tools" ribbon are disabled (all bar
4 - Visual Basic, Run Macro, Add-ins, Make ADE). I desperately need the
Relationship window but its button is disabled. How do I enable it? Or is the
fact that they're disabled indicative of some other problem?

 

[Brendan Reynolds]

I'm developing an ADP project under Access 2007 (SP1, I believe) on
Windows
XP2002 SP3. Most buttons on the "Database Tools" ribbon are disabled (all
bar
4 - Visual Basic, Run Macro, Add-ins, Make ADE). I desperately need the
Relationship window but its button is disabled. How do I enable it? Or is
the
fact that they're disabled indicative of some other problem?

If you're using SQL Server 2008, a lot of the design features just won't
work with that version of SQL Server. See the following link to the Access
Team Blog for more information ...

http://blogs.msdn.com/access/archive/2009/01/21/adp-s-and-sql-server-2008.aspx

 

[Laury G Burr]

Thanks for the link, Brendan, which I'm about to investigate - however, in
this case the back end is SQL Server 2000.

 

[Brendan Reynolds]

Thanks for the link, Brendan, which I'm about to investigate - however, in
this case the back end is SQL Server 2000.

As far as I know, the design features should work with SQL Server 2000, but
I don't have an instance of SQL Server 2000 available to test against. Could
it be a permissions problem?

 

[Laury G Burr]

(Follow-on)

Hmm, that was unnerving!

Well, clearly the client hasn't snuck SQL 2008 in under my nose and not told
me - stored procedures & views designers are working fine; table design works
but is often GLACIAL at opening tables in design view (and then similarly
slow at aligning the columns/lookup data with the field selected - it's a bit
disconcerting to scoot down a 30-field table and get the impression that
every field is the identity field...I sense another question looming!)

Anyway, even if the client wanted to spend more money, your pointer is
sufficient for me to advise against it, at least until Office catches up...

Thanks!

 

[Laury G Burr]

I shouldn't think it's a permissions problem - I can create, alter and run
stored procs, change table design etc as well as doing the real front-end
stuff - and it's the same on all the PCs here. Given that I'm logged on as
Administrator it had better <i>not</i> be a permissiopns issue!!