Re: Cannot Open SQL Server Table in Access.ADP File.
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Mon, 27 Nov 2006 18:12:01 -0500
Many possibilities here, the most probable one would be that you forget to
set the primary key for your tables in your scripts.
Other possiblities would be that you didn't refresh the database window
after creating the tables/views/SP; for example by closing/reopening the ADP
application. This can be important if you are using ADP to recreate the
database instead of using another pgm.
Finally, make sure that you specify dbo as the owner (or the schema under
SQL-Server 2005) for all your tables/ views/ functions/ stored procedures;
otherwise, you can run into a lot of trouble.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Greg" <AccessVBAnet@xxxxxxxxxxxxxxxxx> wrote in message
news:304E2DEF-3D32-41C2-AFE0-CABC5E6985C7@xxxxxxxxxxxxxxxx
I don't expect to get an answer, but I just need to post something.
I have an SQL Server 2005 database which functions properly with my
Access.ADP application. In preparing my backend database for shipment I
ran
the Generate Script Wizard to recreate the SQL Server Database. The Wizard
in
generaly generate a lot of errors of which i could not diagnose, but I was
able to work around. Subsequently, I now have a SQL Script that builds my
new
SQL Server database ready for shipment.
What is happening now has me completely stuck. Several of my tables cannot
be accessed in my Access.ADP application. For example, I have a table
named
tblObject that appears to be completely intact within SQL Server. You can
view the data structure, add data to it from SQL, etc. It appears to be
100%
fine. But, when I attempt to open the table from within the Access DB
Window
I get an error. Several different errors or messages actually.
The first time I click on the table I get a message reporting the "stored
procedure ran successfully but returned no records", even though there are
records in it. Then, If I attempt to open another table, it opens. For
example, I opened tblForm and viewed the table with no problem. After that
then, I go back and double-click on the tblObject table and now I get a
message "the field FormID is read-only" and the table does not open. It
appears the what ever table I successfully opened last will have it's
primary
key displayed in a message box "the field FormID is read-only".
Thus, my database is rendered useless. Has anyone come across such
behavior.
At this point, I am finding the Script Building features for SQL Server
2005
to be unreliable.
Is there a know bug of some sort.
.
- Prev by Date: Re: Performance of ODBC
- Previous by thread: hola
- Index(es):
Relevant Pages
|
