I've created a project and get the message 'Stored procedure executed
successfully but did not return any records' when I try yo open some of the
tables in the SQl database. If I try to open in design view I sometimes get
....'fieldname is read only' message related to a field that isn't even in
the object I'm opening. the same tables and view work fine within the forms
etc. I've designed in the application itself. Creating a new project linked
to the same db has the same problem as does repeating the exercise on a
different PC. I've check the authority on db and everything OK and used query
analyzer with same login to view same tables.
Any ideas? It seems to me that there is something that the database window
checks before opening an object and it doesn't like the way my daatabase is
set up.

Which version of Access and SQL-Server are you using and have you applied
the latest services packs for both?

S. L.

"ge2v" <(E-Mail Removed)> wrote in message
news:CE768B9E-CBC7-4DF6-8F75-(E-Mail Removed)...
> I've created a project and get the message 'Stored procedure executed
> successfully but did not return any records' when I try yo open some of
> the
> tables in the SQl database. If I try to open in design view I sometimes
> get
> ...'fieldname is read only' message related to a field that isn't even in
> the object I'm opening. the same tables and view work fine within the
> forms
> etc. I've designed in the application itself. Creating a new project
> linked
> to the same db has the same problem as does repeating the exercise on a
> different PC. I've check the authority on db and everything OK and used
> query
> analyzer with same login to view same tables.
> Any ideas? It seems to me that there is something that the database window
> checks before opening an object and it doesn't like the way my daatabase
> is
> set up.

Access 2002 SP3 with SQL Server 2000

First, Did you try the command "Refresh" from the View menu when then Tables
listing in the database window is displayed? When you edit your tables
directly in Enterprise Manager, Access doesn't see automatically the changes
and will display funny things if you don't make a refresh. Same thing for
Queries and Stored Procedure: use the Refresh command as well.

Second, since SP2 for WinXP, I had myself some trouble with Access 2002 ADP
(since that, I personally use Access 2003 only) but I don't think this is
related your problem (However, if you have some very strange problems on
some simple things that you cannot resolve, then giving a try with Access
2003 won't be a bad idea at all.)

What is the connection string that you are using? Are you using the OLEDB
driver for SQL-Server or another one?

S. L.

"ge2v" <(E-Mail Removed)> wrote in message
news:B12C316D-4676-401A-B151-(E-Mail Removed)...
> Access 2002 SP3 with SQL Server 2000

Thanks Sylvain - I've done all the general stuff like refreshing and I've
exhausted all th e logical avenues I can think of - it doesn't stop me
working but it's damn annoying. Thinking about it, these symptoms did occur
coincidentally with SP2/3 so I think it's just this badly composed version of
Access. I don't have Access 2003 and I'm loath to try it as my clients are
all Access 2002 and I do not want to open another bag of worms.
The connection string is that generated from the file/connection menu and in
this application I do not override it when the app starts up.

Regards

graham else

Hi,

Just before WinXP - Sp2, I was using Access 2002 exclusively because I
didn't really like this sea of blue that is the scheme color of Access 2003.
However, since Sp2, the kind and number of troubles that I did have with
Access 2002 ADP where so strange and numerous that I don't use it anymore at
all.

With Access 2003, no problemo!

If you don't want to use Access 2003, the only solution I could see
would be to remove SP2.

S. L.

"ge2v" <(E-Mail Removed)> wrote in message
news199CA04-4D7D-4239-A8D6-(E-Mail Removed)...
> Thanks Sylvain - I've done all the general stuff like refreshing and I've
> exhausted all th e logical avenues I can think of - it doesn't stop me
> working but it's damn annoying. Thinking about it, these symptoms did
> occur
> coincidentally with SP2/3 so I think it's just this badly composed version
> of
> Access. I don't have Access 2003 and I'm loath to try it as my clients are
> all Access 2002 and I do not want to open another bag of worms.
> The connection string is that generated from the file/connection menu and
> in
> this application I do not override it when the app starts up.
>
> Regards
>
> graham else
>
>