Link to home
Start Free TrialLog in
Avatar of sarit2002
sarit2002

asked on

How do i configure MSSQL 2005 SP2 to support Sun systems 4.26 in windows vista sp1

Hi there, I have been running sun systems 4.26 as my accounting package for years using MSSQL 7.0, MSDE 2000, MSSQL 2000 server. Recently i acquired a new state of the art dell machine running Windows vista sp1. Loading Sun systems 4.26. on this machine has become a nightmare. I have installed MSSQL 2005 SP2 and SQL Server management studio express. I have configured the ODBC and i can connect to the SQL server using the management studio. I have installed sun systems 4.26 SP11 and configured it. I have restored the INSTALL file and the Report format file and the Reference file without a problem. Now when I restore the Ledger file, i get this error "incorrect syntax near 'ssp_ldg_dbcode' " and i cant proceed from there.

The code for ssp_ldg_dbcode is attached below;
set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
GO
ALTER PROC [dbo].[ssp_ldg_KKT]
   @p1 char(3), @p2 char(2), @p3 char(15), @p4 int, @p5 int, @p6 int, @p7 int,
   @p8 numeric(18,3), @p9 char(1), @p10 char(1), @p11 char(5), @p12 char(5),
   @p13 char(15), @p14 char(25), @p15 int, @p16 int, @p17 int, @p18 int,
   @p19 int, @p20 int, @p21 char(1), @p22 char(10), @p23 char(5), @p24 char(5),
   @p25 numeric(18,9), @p26 numeric(18,3), @p27 char(1), @p28 char(5),
   @p29 char(1),  @p30 char(1), @p31 char(1), @p32 char(1), @p33 char(15),
   @p34 char(15), @p35 char(15), @p36 char(15), @p37 char(15), @p38 char(15),
   @p39 char(15), @p40 char(15), @p41 char(15), @p42 char(15), @p43 int,
   @p44 char(1),  @p45 int, @p46 char(3)
 AS
 begin
  declare @rows      int
  select @rows      = 0
  if @p2 = 'WR'
   begin
    INSERT INTO SALFLDGKKT
     ( ACCNT_CODE, PERIOD, TRANS_DATE, JRNAL_NO, JRNAL_LINE, AMOUNT, D_C,
     ALLOCATION, JRNAL_TYPE, JRNAL_SRCE, TREFERENCE, DESCRIPTN, ENTRY_DATE,
     ENTRY_PRD, DUE_DATE, ALLOC_REF, ALLOC_DATE, ALLOC_PERIOD, ASSET_IND,
     ASSET_CODE, ASSET_SUB, CONV_CODE, CONV_RATE, OTHER_AMT, OTHER_DP,
     CLEARDOWN, REVERSAL, LOSS_GAIN, ROUGH_FLAG, IN_USE_FLAG, ANAL_T0,
     ANAL_T1, ANAL_T2, ANAL_T3, ANAL_T4, ANAL_T5, ANAL_T6, ANAL_T7, ANAL_T8,
     ANAL_T9, POSTING_DATE, ALLOC_IN_PROGRESS, HOLD_REF, HOLD_OP_ID)
    VALUES
     ( @p3 , @p4 , @p5 , @p6 , @p7 , @p8 , @p9 , @p10 , @p11 , @p12 , @p13 ,
       @p14 , @p15 , @p16 , @p17 , @p18 , @p19 , @p20 , @p21 , @p22 , @p23 ,
       @p24 , @p25 , @p26 , @p27 , @p28 , @p29 , @p30 , @p31 , @p32 , @p33 ,
       @p34 , @p35 , @p36 , @p37 , @p38 , @p39 , @p40 , @p41 , @p42 , @p43 ,
       @p44 , @p45 , @p46)
   end
  if @p2 = 'RW'
   begin
     UPDATE SALFLDGKKT SET
       ACCNT_CODE = @p3, PERIOD = @p4, TRANS_DATE = @p5, JRNAL_NO = @p6,
       JRNAL_LINE = @p7, AMOUNT = @p8, D_C = @p9, ALLOCATION = @p10,
       JRNAL_TYPE = @p11, JRNAL_SRCE = @p12, TREFERENCE = @p13,
       DESCRIPTN = @p14, ENTRY_DATE = @p15, ENTRY_PRD = @p16, DUE_DATE = @p17,
       ALLOC_REF = @p18, ALLOC_DATE = @p19, ALLOC_PERIOD = @p20,
       ASSET_IND = @p21,ASSET_CODE = @p22, ASSET_SUB = @p23, CONV_CODE = @p24,
       CONV_RATE = @p25, OTHER_AMT = @p26, OTHER_DP = @p27, CLEARDOWN = @p28,
       REVERSAL = @p29, LOSS_GAIN = @p30, ROUGH_FLAG = @p31,
       IN_USE_FLAG = @p32, ANAL_T0 = @p33, ANAL_T1 = @p34, ANAL_T2 = @p35,
       ANAL_T3 = @p36, ANAL_T4 = @p37, ANAL_T5 = @p38, ANAL_T6 = @p39,
       ANAL_T7 = @p40, ANAL_T8 = @p41, ANAL_T9 = @p42, POSTING_DATE = @p43,
       ALLOC_IN_PROGRESS = @p44, HOLD_REF = @p45, HOLD_OP_ID = @p46
     WHERE  ACCNT_CODE = @p3 AND PERIOD = @p4 AND TRANS_DATE = @p5 AND
       JRNAL_NO = @p6 AND JRNAL_LINE = @p7
    select @rows = @@ROWCOUNT
   end
  if @p2 = 'DL'
   begin
      DELETE FROM  SALFLDGKKT
        WHERE  ACCNT_CODE = @p3 AND PERIOD = @p4 AND TRANS_DATE = @p5 AND
        JRNAL_NO = @p6 AND JRNAL_LINE = @p7
      select @rows = @@ROWCOUNT
   end
  if @rows = 0
    if @p2 = 'RW'
      raiserror 50100
      'Stored procedure (rewrite) on SALFLDGKKT failed - row not found'
    else
      if @p2 = 'DL'
        raiserror 50100
        'Stored procedure (delete) on SALFLDGKKT failed - row not found'
 end

Open in new window

Avatar of reb73
reb73
Flag of Ireland image

The code listed is for ssp_ldg_KKT while you have mentioned that the error refers to ssp_ldg_dbcode..

The error 'incorrect syntax near ...' usually occurs in front-end applications that do not declare a correct command type when invoking a backend procedure.. I'm not sure if can be addressed by changing anything in the SQL backend..
Avatar of sarit2002
sarit2002

ASKER

KKT is the dbcode. That was a slight mixup on my part.
>>  Windows vista sp1.

32 bit or 64 bit?
32 bit
Shoots my idea down. I was thinking 64 vs 32 bit ODBC drivers.
Infor Technical confirmed that Windows Vista is not a supported platform with our current SunSystems version
ASKER CERTIFIED SOLUTION
Avatar of sarit2002
sarit2002

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
for additional information on how to solve this problem logon to http://mydansoft.blogspot.com.