By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,481 Members | 979 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,481 IT Pros & Developers. It's quick & easy.

Can't Create Linked Server SP in ADP

P: n/a
I created a stored procedure to update a table on a linked server from a
table in my local server. Both servers are SQL 7, and the linked server is
accessed through the Internet. When I tried to create the stored procedure
using an Access 2000 ADP file, the save command would continually time out.
However, when I went into Enterprise Manager and created the stored
procedure there, it saved instantly. Once the SP was saved, it could be run
from the ADP file without any problem. But neither creating nor modifying
the SP would work through the ADP file.

Any ideas on why the ADP file would not be able to create or modify the SP,
but would be able to run it, or any ideas about what might be able to be set
in the ADP file to enable it?

May 15 '06 #1
Share this Question
Share on Google+
2 Replies

P: n/a
you got your Access 2000 patched to the latest service pack?

ps - are you using the 'create proc' syntax to make the sproc?
you need to spell out 'procedure' and not abbreviate

i swear i would beat the living crap out of an Access PM if i found
one. i mean how in the heck do they sit there with their rolex; their
stock options and their bmw-- they sit there any miss a bug like that?

they should retroactively be terminated and or shot on site.

dipshits running the show in redmond.

May 16 '06 #2

P: n/a
I have had similar problems with the ADP. Right now I am having a write
conflict error on update of a particular table. The problem is stemming
from some null fields in another table that is part of an update trigger
for the table I have the problem with. For creating SPs from the ADP,
use the ADO command object.

cmd.CommandText = "Create Proc stp_something As ..."

The ADP is a somewhat convenient interface for Sql Server, but as my
projects get more sophisticated, the ADP is having issues. I am
starting to migrate more of my ADP apps to DotNet apps and using Sql
Server Reporting Services. Although, the ADP is still the easiest
interface for doing Sql Server Reporting operations. That is at least
the one redeeming quality that Access has - ease of reporting - will be
very difficult to beat. In the meantime, I am performing less and less
data operations through Access.


*** Sent via Developersdex ***
May 16 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.