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?
Thanks!
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.
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.
Rich
*** Sent via Developersdex http://www.developersdex.com ***