ADP Problem

[rudy susanto]

Hi All,

I have a server that contains sqlserver 2000 and ms access 2000.
Everything were working fine when i ran my adp file in the server side,
and i faced some problem when i ran it on the client computer.

After checking my adp file, i found all of my stored procedures added by
comma and number at the behind. For example i have a stored procedure
p_rpt_supp_list in the server, but i found p_rpt_supp_list;1 in my ms
access.

Does anyone know how to solve this?
Thanks in advance,
Rudy
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[John Bell]

Hi

The number is the version number see:
http://msdn.microsoft.com/library/de...reate_4hk5.asp

This can be seen as the number column in syscomments see books online:
mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\tsq
lref.chm::/ts_sys-c_2y2b.htm

According to SQL Server 2000 Performance Tuning Technical Reference (P322)
;1 is assummed no number is stated. If version 1 is hard coded, then the
only way I can think of re-creating a version 1 is to drop all versions of
the procedure and recreate it (without a version number of explicitly at
version 1).

John
"rudy susanto" <rs*******@yahoo.com.sg> wrote in message
news:40***********************@news.frii.net...

Hi All,

I have a server that contains sqlserver 2000 and ms access 2000.
Everything were working fine when i ran my adp file in the server side,
and i faced some problem when i ran it on the client computer.

After checking my adp file, i found all of my stored procedures added by
comma and number at the behind. For example i have a stored procedure
p_rpt_supp_list in the server, but i found p_rpt_supp_list;1 in my ms
access.

Does anyone know how to solve this?
Thanks in advance,
Rudy
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[rudy]

Hi John,

I never created any stored procedures using ; separator.

I always drop the procedure if it's exists before creating it.

The problem is office 2k (without service pack) but everything is
working fine in office xp.

Thank very much for your response John. :)

Warmest Regards,
Rudy

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[John Bell]

Hi

I am not sure what is happening then as your stored procedures will
always be a version 1. You may want to try SQL Profiler and view what
commands are being sent to the server. If you can update/patch the
version of office it may help.

John

rudy <ru**@mail.com> wrote in message news:<40*********************@news.frii.net>...

Hi John,

I never created any stored procedures using ; separator.

I always drop the procedure if it's exists before creating it.

The problem is office 2k (without service pack) but everything is
working fine in office xp.

Thank very much for your response John. :)

Warmest Regards,
Rudy

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Erland Sommarskog]

rudy susanto (rs*******@yahoo.com.sg) writes:

I have a server that contains sqlserver 2000 and ms access 2000.
Everything were working fine when i ran my adp file in the server side,
and i faced some problem when i ran it on the client computer.

After checking my adp file, i found all of my stored procedures added by
comma and number at the behind. For example i have a stored procedure
p_rpt_supp_list in the server, but i found p_rpt_supp_list;1 in my ms
access.

That may just be the way Access lists the procedures. As John said, the ;1
is there. Saying

EXEC my_proc;1

is the same as

EXEC my_proc

--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

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