BUG: Oracle Code Might Appear IncorrectlyID: Q191043
|
Oracle stored procedures, functions, and trigger source code might appear without line breaks or might appear incorrectly justified in the Source view editor. This is a visual problem only. This problem should not affect the functionality of the code object.
To avoid this problem, do one of the following:
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
CREATE OR REPLACE PROCEDURE PROCEDURE2 (A DEC, B DEC, C DEC) AS BEGIN
RETURN; END;
CREATE OR REPLACE PROCEDURE PROCEDURE2 (A DEC, B DEC, C DEC)
AS BEGIN RETURN; END;
CREATE OR REPLACE PROCEDURE PROCEDURE2
(A DEC, B DEC, C DEC)
AS BEGIN RETURN; END;
CREATE OR REPLACE PROCEDURE PROCEDURE2
(
A DEC,
B DEC,
C DEC
)
AS BEGIN RETURN; END;
CREATE OR REPLACE PROCEDURE PROCEDURE2 ( A DEC, B DEC, C DEC )
AS BEGIN RETURN; END;
EXPECTED RESULT: Source should be consistent with what was saved as
follows:
CREATE OR REPLACE PROCEDURE PROCEDURE2
(
A DEC,
B DEC,
C DEC
)
AS BEGIN RETURN; END;
Additional query words:
Keywords : kb3rdparty kbOracle kbVisID600 kbVisID600bug kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: May 25, 1999