Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

refresh of Enterprise Explorer

2 posts in General Discussion Last posting was on 2008-04-25 06:57:01.0Z
Andreas Gerats Posted on 2008-04-22 15:09:02.0Z
Sender: 4e17.480da9c0.1804289383@sybase.com
From: Andreas Gerats
Newsgroups: sybase.public.workspace.general
Subject: refresh of Enterprise Explorer
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <480dff8e.55cb.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Apr 2008 08:09:02 -0700
X-Trace: forums-1-dub 1208876942 10.22.241.41 (22 Apr 2008 08:09:02 -0700)
X-Original-Trace: 22 Apr 2008 08:09:02 -0700, 10.22.241.41
Lines: 27
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:689
Article PK: 1088364

Hi,

I created a procedure with a recursive procedure call. On
saving this procedure to the database server within
procedure editor ("Save to Server"), the following error
message is displayed:

Msg 2007, Level 11, State 1:
Server 'cread03', Procedure 'dbo.proc_pds_logging_ins', Line
64:
Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'proc_pds_logging_ins'. The stored procedure will still be
created.

This is expected so far and the procedure is created within
ASE, but procedure editor in WorkSpace still indicates that
there are changes to save and procedure within WorkSpace
Enterprise Explorer is not refreshed. You can easily
reproduce this when closing the procedure without saving and
reopening it with Enterprise Explorer. Your changes are gone
in the editor until you are doing an explicitely refresh
within Enterprise Explorer and reopen procedure again.
This can lead to different sources in ASE versus WorkSpace.

Thanks and best regards
Andreas


Daniel Huang Posted on 2008-04-25 06:57:01.0Z
Reply-To: "Daniel Huang" <lihuang@sybase.com>
From: "Daniel Huang" <lihuang@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <480dff8e.55cb.1681692777@sybase.com>
Subject: Re: refresh of Enterprise Explorer
Lines: 58
Organization: Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <481180bd@forums-1-dub>
Date: 24 Apr 2008 23:57:01 -0700
X-Trace: forums-1-dub 1209106621 10.22.241.152 (24 Apr 2008 23:57:01 -0700)
X-Original-Trace: 24 Apr 2008 23:57:01 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:692
Article PK: 1088371

Hi, Andreas:

Procedure schema editor will keep dirty status if exception happens when
procedure is saved to server.
For your case, just like you desribed, you need do the following to work
around the problem:
1. Close the dirty SP editor,
2. Go to Enterprise Explorer to refresh the stored procedures folder,
3. Re-open the stored procedure, the previouse changes will be displayed.

Similarly, if the procedure is created by external tools like isql, you need
to refresh procedure folder in Enterprise Explorer for sync with server.
Enterprise Explorer will not sync with server automatically.

--
Thanks and regards,

Daniel Huang

Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Email: lihuang@sybase.com

<Andreas Gerats> wrote in message
news:480dff8e.55cb.1681692777@sybase.com...
> Hi,
>
> I created a procedure with a recursive procedure call. On
> saving this procedure to the database server within
> procedure editor ("Save to Server"), the following error
> message is displayed:
>
> Msg 2007, Level 11, State 1:
> Server 'cread03', Procedure 'dbo.proc_pds_logging_ins', Line
> 64:
> Cannot add rows to sysdepends for the current stored
> procedure because it depends on the missing object
> 'proc_pds_logging_ins'. The stored procedure will still be
> created.
>
> This is expected so far and the procedure is created within
> ASE, but procedure editor in WorkSpace still indicates that
> there are changes to save and procedure within WorkSpace
> Enterprise Explorer is not refreshed. You can easily
> reproduce this when closing the procedure without saving and
> reopening it with Enterprise Explorer. Your changes are gone
> in the editor until you are doing an explicitely refresh
> within Enterprise Explorer and reopen procedure again.
> This can lead to different sources in ASE versus WorkSpace.
>
> Thanks and best regards
> Andreas