Running Stored Proc inside of Access and getting error

Running Stored Proc inside of Access and getting "The stored procedure
executed successfully but did not return records". When I run in Query
Analyzer it runs just fine. The Stored Proc is as follows:
CREATE PROCEDURE MAINT_EditorActivitybyTime (@.Enter_Start_Date_
smalldatetime, @.Enter_End_Date_ smalldatetime)
AS
DROP TABLE TEMP_MA_Node
--stored proc to create one table from MA_Node and MA_Node_Status10
DECLARE @.Temp_Node_Status10 table(NodeID bigint, NodeName nvarchar(100),
TypeID int, Status tinyint, OwnerID int, Url nvarchar(2048), Path
nvarchar(1000))
INSERT INTO @.Temp_Node_Status10
SELECT NodeID, NodeName, TypeID, Status, OwnerID, Url, Path
FROM MA_Node_Status10
SELECT *
INTO TEMP_MA_Node
FROM @.Temp_Node_Status10
INSERT INTO TEMP_MA_Node
SELECT NodeID, NodeName, TypeID, Status, OwnerID, Url, 'Live'
FROM MA_Node
SELECT dbo.MA_Change.CreateTime, dbo.MA_User.Email,
dbo.MA_Change.ChangeNodeID, dbo.MA_Change.DraftAction, TEMP_MA_Node.NodeName
,
TEMP_MA_Node.TypeID, TEMP_MA_Node.Status
FROM dbo.MA_Change INNER JOIN
dbo.MA_User ON dbo.MA_Change.ModifyUser =
dbo.MA_User.UserID LEFT OUTER JOIN
TEMP_MA_Node ON dbo.MA_Change.ChangeNodeID =
TEMP_MA_Node.NodeID
WHERE (dbo.MA_Change.CreateTime BETWEEN @.Enter_Start_Date_ AND
@.Enter_End_Date_)
ORDER BY dbo.MA_User.Email, dbo.MA_Change.CreateTime
GO
It also returns data in Query Analyzer like this:
2006-01-10 11:40:00.927 andy1221 198643 2 asdfasdf 4 0
2006-01-10 11:41:35.553 andy1221 198644 2 Lycos
Directory>Reference>Education>Distance Learning 4 0
2006-01-10 11:44:39.963 andy1221 198644 4 Lycos
Directory>Reference>Education>Distance Learning 4 0
2006-01-10 11:45:02.637 andy1221 30064 4 Reference Education Distance
Learning 4 0Hi Andy,
use
SET NOCOUNT ON
at the beginning of the SP
and
SET NOCOUNT OFF
as the last statetement of your proc.
If you use the sp like yours you will recieve multiple recordsets in Access.
HTH ;-)
Gru, Uwe Ricken
MCP for SQL Server 2000 Database Implementation
GNS GmbH, Frankfurt am Main
http://www.gns-online.de
http://www.memberadmin.de
http://www.conferenceadmin.de
________________________________________
____________
dbdev: http://www.dbdev.org
APP: http://www.AccessProfiPool.de
FAQ: http://www.donkarl.com/AccessFAQ.htm

Running SQL Server 6.5 on Win2K Server?

Is anyone here successfully running SQL Server 6.5 in a Windows 2000
Server??
We tried to and had some runtime problems relative to tempdb.(cdavis10717@.comcast.net) writes:
> Is anyone here successfully running SQL Server 6.5 in a Windows 2000
> Server??
> We tried to and had some runtime problems relative to tempdb.

I seem to recall that it is supported, provided that you have SP5a of
SQL 6.5.

But I have to admit that I once attempted to install SQL 6.5 on Win 2000
Pro, and I wasn't successful. When you say it, it might have been an
issue with tempdb. In my case, the problems occurred already during
installation.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog wrote:
> (cdavis10717@.comcast.net) writes:
> > Is anyone here successfully running SQL Server 6.5 in a Windows
2000
> > Server??
> > We tried to and had some runtime problems relative to tempdb.
> I seem to recall that it is supported, provided that you have SP5a of
> SQL 6.5.
> But I have to admit that I once attempted to install SQL 6.5 on Win
2000
> Pro, and I wasn't successful. When you say it, it might have been an
> issue with tempdb. In my case, the problems occurred already during
> installation.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp

Thank you. Yes, the running SQL Server 6.5 choked on tempdb. And even
starting sql server in minimal mode failed since tempdb would not
allocate in RAM. Oh, well, we are going back to SQL 6.5 on NT until we
can determine the databases that must be upgraded or dropped.
thank you again.|||(cdavis10717@.comcast.net) writes:
> Thank you. Yes, the running SQL Server 6.5 choked on tempdb. And even
> starting sql server in minimal mode failed since tempdb would not
> allocate in RAM. Oh, well, we are going back to SQL 6.5 on NT until we
> can determine the databases that must be upgraded or dropped.
> thank you again.

Allocating tempdb in RAM? Do you have that feature on? Or is that something
which happens when you start in single-user mode? I'm not using 6.5
much these days...

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Running SQL 7.0+SP4 on XP Pro...

Is anyone doing this successfully? Were there any problems getting up and
running? Any software patches needing to be downloaded to make this happen?

We have been using Access. I know, it's cheesy, but for the simplistic data
model we've used up until now it worked. However, we've outgrown the simple
data model and now need more full-fledged queries and stored procs).

I have an old copy of SQL Server 7.0 laying around but wanted to get some
feedback from folks who have been using it with XP Pro before installing and
getting into a bunch of potential headaches. Any feedback concerning this
both welcomed and appeciated in advance.

Cheers!David,

It works fine, however it will install the desktop edition since you are not
running a version of Windows Server. Also, if you are good in Access, there
are a couple ways in which you can still leverage that knowledge. I favor
using Access Projects for group apps when the budget doesn't have room for
..NET. However, you can use the regular old .mdb's and link the SQL tables
to do things the way you are used to doing them.

Good luck!

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz

"David L. Rice" <dali_llama@.comporium.net> wrote in message
news:bp5o8h$109e$1@.news3.infoave.net...
> Is anyone doing this successfully? Were there any problems getting up and
> running? Any software patches needing to be downloaded to make this
happen?
> We have been using Access. I know, it's cheesy, but for the simplistic
data
> model we've used up until now it worked. However, we've outgrown the
simple
> data model and now need more full-fledged queries and stored procs).
> I have an old copy of SQL Server 7.0 laying around but wanted to get some
> feedback from folks who have been using it with XP Pro before installing
and
> getting into a bunch of potential headaches. Any feedback concerning this
> both welcomed and appeciated in advance.
> Cheers!