Why does Access 2007 make many calls to SQL Server looking for Extended Properties?

I have seen some posts on the internet (i.e. Expert Exchange) regarding this, but would like to try a new question. I am having the same problem.

I have an Access 2007 project that was once Access 2003 project. The application connects to a SQL Server 2000 database. Everything worked great in Access 2003, but then I upgraded to Access 2007. Now, the Access application makes about 5,000 calls per minute to the database and slows performance down, with intermittent delays. SQL Profiler shows this call to the DB:

SELECT *, sql_variant_property(value, 'basetype') AS type FROM ::fn_listextendedproperty(N'MS_Description',N'user',N'dbo',N'table',N'[ TABLE NAME ',NULL,NULL)

The SQL Server DB has about 100 tables. For 31 of the tables, a call is made by Access with its respective table name in the SELECT statement above. Some articles suggest the Extended Properties in tables are the problem and need to be removed. Others say its the foreign keys used in the joins of the T-SQL and that they should  be removed. Importing to a new ADP is not possible, as I tried and many times. After importing, the forms are unrecognizable and cant be repaired.

Do you have other suggestions? What else can I try?
gtrappAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

borkiCommented:
Hi gtrapp

Not sure what is causing this, I am just at the start of converting an .adp from Access 2002 to 2007. So far we have not found such an issue, although only a few selected users have been running the 2007 version.

The extended property that you see in the profiler is what you use as a comment for the field in the Access table designer. Perhaps you could try to delete this? I think Access uses the field to display information in the status bar when you generate forms, so maybe it still uses them at run-time?

How many users are running your fornt end to have 5000 calls/minute?

Keep us posted

Felix
0
gtrappAuthor Commented:
There is one Access front-end application making 5,000 calls. If I deploy this, there will be about 15 users. Also, there is another Access front-end application that behaves the same way. Currently, no one is using the applications now, but if the users did, I think the DB server would choke. I will take a look at the comments.
0
gtrappAuthor Commented:
I checked comments in Design View and did not see any. I check about 10 tables, of the 31 that were named in the SELECT statement above.

Microsoft has been working on this for 4 weeks now. Like you said, very few people with this people, which means MS is not going to fix it for a very long time.

0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

borkiCommented:
So you are sayinging you lodged the issue with MS Support? 4 weeks sounds pathetic.

I want to check this out now myself, even though my tests have not shown any performance issues, but then I have not really looked for this issue and it might have gone unnoticed.

What filter did you set up in SQL Profiler?
0
gtrappAuthor Commented:
Yes, its been 4 weeks now and slowly getting to be 5 weeks. MS says they have esculated the issue.

I did not use any filter with the SQL Profiler.
0
gtrappAuthor Commented:
MS has found a bug with my Access database and in 3-4 months will supply a hot-fix. I was able to import the old code, reports, forms, and modules to a new Access 2007 ADP file, which avoided the 5,000 calls to the DB bug.
0
borkiCommented:
Good news! I have been using .ADPs for a number of situations and have never experienced your issue.

However, I use the steps of re-import once a month on most DBs regardless of any issues, as it keeps the filesize of the ADP down. After this step, my bigest ADP is about 8 Mb, making various changes over the month it ends up about 18 Mb (after 2x compile, compact & repair)! Clearly there are issues with bloat!

I will look out for the tech details of the hot-fix.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Satu7nineCommented:
Borki - I'm seeing the same issue you raised here.

Did you ever get anywhere with Microsoft in terms of a hotfix?
0
gtrappAuthor Commented:
No. I imported forms, code, reports and such all to a new Access 2007 file. That fixed the problem.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.