Access 2007 ADP and SQL

[Guest]

We created an Access ADP project in Access 2003 connected to a SQL2000
backend which was working fine.

If we open it in Access 2007 its extremely slow on startup and opening forms
etc.

We did a sql trace and discovered when using ACCESS 2007 that the following
TSQL instruction is being executed

(

SELECT *, sql_variant_property(value, 'basetype') AS type FROM
::fn_listextendedproperty(N'MS_Description',N'user',N'dbo',N'function',N'qryMarketingTransactions',NULL,NULL)

)

for what seems to be every object in the database. In ACCESS 2003 none of
these commands are being executed. I've noticed in other forums that other
people have experienced the same issues - but with no solution offered

Anybody get any suggestions?

 

[Sylvain Lafontaine]

Someone has suggested that this problem of slowness might be diminished
after starting from a blank ADP project; so maybe you could give it a try
and inform us.

Personnally, I didn't have the occasion of testing this theory by myself yet
because I still don't have installed Access 2007 precisely because I had
this exact same problem with the Beta version.

With this problem, A2007 is totally useless to me as none of my clients will
accept this situation.

 

[Adrian]

Does anyone know if this problem also occurs with Access 2007 and SQL Server
2005?

Thanks,

Adrian

 

[aaron.kempf]

I've only noticed it being really really slow when you've got hundreds
of tables or something

I just swear; if they made a hash index and stored the csname for
objects; I thnk that would take care of it

I just swear; when it has to scan sysobjects and sysobjects has 2,000
objects in it is when i see this slowness

-Aaron

 

[Guest]

Yes its the same with SQL 2005. I backed up my database up and restored it to
SQL2005 and repointed the ADP to the SQL2005 version, still the same.

 

[aaron.kempf]

I can't even get Office 2007 to _OPEN_

it keeps on throwing some error about how I can't run it on a terminal
server. Yes, I have tried it locally-- at home instead of across a
terminal.

I just find it humorous.. I'm not using a terminal session why does
Office give a shit if I have terminal enabled?

-Aaron

 

[Sylvain Lafontaine]

And do you know what happens with the new format for ADP, the one with the
extension .accdp?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

Yes its the same with SQL 2005. I backed up my database up and restored it
to
SQL2005 and repointed the ADP to the SQL2005 version, still the same.

 

[Norman Yuan]

*.accdp? Searched my Access2007, did not find such a file type in
Access2007's open/new file dialog box. No subject/index found in
Access2007'e help either.

Besides native *.accdb format, Access2007 also support

*.accdt - template
*.accdc - singed package
*.accda - add-in

 

[aaron.kempf]

I can't get office to open; it complains about being run on a terminal
server

I mean; SERIOUSLY here guys

is UNNECESSARY COMPLEXITY either simple or necessary?

-Aaron

 

[drinski67]

It is still slow. Even after SP1 installed.

When you open siple form with Server Filter by Form property set to YES, form doesn't work.

Crashes, hangs, crashes, hangs...

I have 28 hangs and crashes with MSO Access 2007 ADP. Same app works fine in MS Access 2003 SP3.

I am reporting to Microsoft about problems regulary, but, they don't have solution for MSO Access 2007 ADP still...

MSO Access 2007 ADP looks to me unusable. Even after SP1 installed.

Is there any solution for MSO Access 2007 ADP connected to MS SQL Server 2005 Express?