Hi,

I use an Access Project as a front end for my database, which is in SQL
Server 2000. Everything is working fine in Access 2003. However, I just
upgraded one machine to Access 2007, and now Access cannot open any query or
table in design view - I get an error saying that the object does not exist.
This error will either reference the query or table by name, or will
reference a cryptic SQL Statement that mentions Sharepoint. However, I can
view the results of the query or contents of the table just fine. Is there
something that I need to do in the database for it to open in Access 2007? Or
is the only solution an upgrade to SQL Server 2005?

Thanks,
I. Kinal

Dear Kinal,

Thank you for posting here.

From the problem description of the post you submitted, my understanding
is: the error message "Object does not exists" will be received if we open
query or table in Design View after upgrading to Access 2007. If I have
misunderstood about your concern, feel free to let me know.

Before going further, I would like to explain that Office Access offers two
ways to connect to SQL Server data: linking to SQL Server and Access Data
Projects (ADPs). In order to ensure the current status, please first
confirm with me the way to connect to SQL Server is MDB or ADP.

Thank you for taking time to help me check above information.

At the same time, to isolate the cause of the issue, it is recommended that
we create a new Access 2007 database and then link table to the SQL Server
2000 to check if issue still occurs in this newly created Access file. I
have included the summary of the steps for you:

1. Create a new Access 2007 Database
2. Linking to SQL Server
3. Open anyone of the table in the Design Mode and then check if the issue
still persists in this newly created table.

Related Information
===================
Migration considerations for Access 2007
http://technet2.microsoft.com/Office...1c-446a-8ff2-2
21769a58ba51033.mspx?mfr=true

If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Hi,

Thank you for your response.

The Access database in questions is an Access Project file. I tried your
suggestion of creating a new, normal database and linking a table from the
SQL Server - I was able to open the table's design view without a problem.

Here is the beginning of the error that I get when trying to open the same
table's design view in the Access project: Microsoft Office Access can't find
the object 'Select *, sql_varient_property(value, 'basetype') as type from
::fn_listextendedproperty(N'ms_displayviewsonshare pointsite',N'user',N'

Is it looking for that function? Why??

Thanks,
I. Kinal

"Adams Qu [MSFT]" wrote:

Dear Kinal,

Thank you for your reply.

You have indicated that the Access database is an Access Project file (ADP)
and we are able to open the table's design view without a problem via
linking a table feature in normal database (MDF). But the following error
occurs when we attempt to open the same table's design view in the Access
project:

Microsoft Office Access can't find the object 'Select *,
sql_varient_property(value, 'basetype') as type from
::fn_listextendedproperty(N'ms_displayviewsonshare pointsite',N'user',N'

If I have misunderstood the latest information you provided, please let me
know.

Based on the Book Online, this function is used to get the extend property
of the database and this function may be called by the Access program when
we open in the design view so as to get the relevant data type.

However, I have conducted much test on my test machine (connect Access 2007
to SQL Server 2000 database) but cannot reproduce such behavior. According
to the error message, I suspect that the function returns the blank value
so that SQL server cannot get the type of the data in the design view. We
can try to run this SQL statement on the SQL Server 2000 Query Analyzer to
check if what result is returned or just a blank result.

In addition, as you have previously attempted to link a table in SQL Server
2000 in the newly created database, I also suggest we create a new ADP file
in Access 2007 and then point it to the SQL Server 2000 to check if the
issue also occurs in that newly created ADP file.

1. If the issue does not occur to the new ADP file, we can simply use this
newly created ADP file in the further. We can conclude that the issue is
caused by the connection parameter and the issue is resolved after we
create a new file and rebuild the connection.

2. However, if the issue still persists in the new ADP file, please try to
modify the connection and make it connect to the other database such as
Northwind or the newly created database to test if the issue is related to
database specified.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------

Hi,

I tried creating a new ADP and connecting it to my existing database - this
produced the same error. I then tried creating a new database, and
redirecting the ADP to the new database. Then, when I tried to create a new
table in the new database, I immediately got a similar error - Microsoft
Office Access can't find the object table1.

I checked and I found that the function fn_listextendedproperty does exist
in my Master database.

Thanks,
I. Kinal

"Adams Qu [MSFT]" wrote:

Dear Kinal,

Thank you for posting here.

I understand the issue even occurs when we create a new ADP file and make
it point to a new database on SQL Sever.

With your efforts and cooperation, I think we should have narrowed down the
cause of this problem. When the issue even occurs when we connect to a new
database, the problem seems to be on the Access program side.

As you have mentioned that the Office 2007 program was upgraded from Office
2003, let's test the issue on clean-installed Office 2007 (Access 2007)
program on an alternative machine. NOTE: Please first also connect the ADP
file to the newly created database for the troubleshooting purpose.

Is our issue resolved?

However, if the same behavior still occurs, please download the SQL Server
2005 Express Edition (Free) from the following download link and then
install it on a test machine. Please check if there is any problem when
connecting the adp file to this newly installed SQL Server 2005 database.
http://www.microsoft.com/downloads/d...9b5-0b07-4448-
8848-dcc397514b41&DisplayLang=en

NOTE: By default, SQL Server 2005 Express Edition does not allow the remote
connection. Please refer to the following KB article on how to configure it
to allow the remote connection.

How to configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/kb/914277

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
<7A37D94D-DC74-41CE-8D5C-7C15F3252D67 (AT) microsoft (DOT) com>
<XXVeUQWvHHA.2220 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>

Hi,

OK, I tested connecting from a different machine with Access 2007 installed,
and it worked fine, without this problem. So it does appear to be a problem
with the Access installation on this particular computer. What would be the
best way to solve this?

Thanks,
I. Kinal

"Adams Qu [MSFT]" wrote:

Dear Kinal,

Thank you for your reply.

I am glad to hear that the connection works fine on a different machine
with Access 2007 installed.

At this stage, we can narrow down the issue to the local settings of Office
program.

I suggest we test the issue in the new user account. Please NOTE: Most of
the Office settings are stored in the user profile. By creating the new
user account, we can determine if the problem is caused by the user's
office setting.

1. Log on the problematic machine as a newly created user account (Windows
account)
2. Create the ADP file and then make the connection again to check if the
connection can be successful.

If the issue does not occur to the newly created account, please log on the
original user account and then open Access 2007, Click Help-> Diagnose the
problem and then select Setup Diagnose to fix the user personal settings'
problem in Office.

However, if the issue also occurs to the new user account, we may consider
backing up some important data and then clean install the Office program.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
<7A37D94D-DC74-41CE-8D5C-7C15F3252D67 (AT) microsoft (DOT) com>
<XXVeUQWvHHA.2220 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<3F8BC7C0-76DC-407D-9C5C-666BE32D227F (AT) microsoft (DOT) com>
<rE14RIfvHHA.3972 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>

Dear Kinal,

How's everything going?

I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
<7A37D94D-DC74-41CE-8D5C-7C15F3252D67 (AT) microsoft (DOT) com>
<XXVeUQWvHHA.2220 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<3F8BC7C0-76DC-407D-9C5C-666BE32D227F (AT) microsoft (DOT) com>
<rE14RIfvHHA.3972 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<1736DCCC-46E6-4DDA-9E89-31ED144C8B5B (AT) microsoft (DOT) com>

Hi,

I apologize for not responding sooner. The computer has been misbehaving for
the past several days, and I have determined that I need to replace the hard
drive. After that I will perform a clean installation of Office 2007, which
will most likely fix the problem. If it does not, I will post back here.

Thanks,
I. Kinal

"Adams Qu [MSFT]" wrote: