Viewing 15 posts - 1,591 through 1,605 (of 2,043 total)
some in the role db_securityadmin can assign execute permission.
February 16, 2006 at 4:47 am
Welcome
the syntax is
EXECUTE mylinkedserver.myremotedatabase.myremoteobjectowner.USP_MYREMOTESTOREDPROCEDURE @param1=....
February 16, 2006 at 4:39 am
CREATE STORED PROCEDURE dbo.USP_CLASSTRACK_PIVOT_QUARTER
AS
SET NOCOUNT ON
SELECT classcode,
SUM(CASE Quarter WHEN 'winter' THEN Amount ELSE 0 END) AS 'Count Winter',
SUM(CASE Quarter WHEN 'spring' THEN Amount ELSE 0 END) AS 'Count...
February 15, 2006 at 2:18 pm
where did you declare rstStoredProc ?
you can test if rstStoredProc exist with
if not(rstStoredProc is nothing)
*move
' Spit out our data which I pull out of the recordset.
'Response.Write Trim(rstStoredProc("Supervisors"))
'Response.Write " "
'Response.Write...
February 15, 2006 at 2:01 pm
for update you need to specify the update command also
for the microsoft help on dataadapter.update
February 15, 2006 at 1:54 pm
Perhaps to save on the amount of I/O that has to be done to reclaim the unused space.
New records will be probably created using the new size.
February 15, 2006 at 11:23 am
could be permissions, referential integrity
Are you using a stored proc for the delete command or dynamic sql?
(number of output parameters match?)
February 15, 2006 at 10:56 am
have a look at
http://www.davidpenton.com/testsite/scratch/disconnected.command.asp
basically
rs=adocmd.Execute
while not rs.eof '*retrieving all records*
rs.movenext
wend
February 15, 2006 at 10:53 am
Hmm, the image doesn't show up.
Can you post your report sql + table definitions & some sample data?
*calling a stored procedure from asp
http://support.microsoft.com/kb/q164485/
*creating a stored procedure
CREATE PRODECURE dbo.USP_MY_PROCEDURE
(@Param1 as...
February 15, 2006 at 10:40 am
server: =mssql10.oneandone.co.uk
login id = dbo152591563
password= dbo152591563's password
Can you verify through the admintool that the user dbo152591563 can login?
February 15, 2006 at 10:33 am
Right,
Because in sql server 2000 the jobs are "attached" to a servername to allow multiple instances.
You can script out all jobs, or you can adjust originating_server in msdb.dbo.sysjobs
February 15, 2006 at 10:26 am
rewrite as
docmd.setwarnings false
docmd.openquery "xxx"
docmd.openquery "xxx"
docmd.setwarnings true
February 14, 2006 at 1:38 pm
Welcome.
I'm having trouble seeing your pictures.
If the sql server is the default instance, the servername is likely to be your hostname.
What connectionstring are you using?
Is this using the Access upsizing...
February 14, 2006 at 1:35 pm
February 14, 2006 at 9:37 am
Viewing 15 posts - 1,591 through 1,605 (of 2,043 total)