›
Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.

v3.4.6 install SRP_EDITOR_SERVICES

MattCrozierMattCrozier
in SRP Editor
I've just installed SRP Editor v3.4.6 into OI10.2.3(b2), and tried compiling one of the Super Strings examples. It seems I'm missing the SRP_EDITOR_SERVICES program? It's being called from SRP_Editor_Compile_Services().

Cheers, M@
«1

Comments

  • AusMarkBAusMarkB
    Do you still have the srputilities.dll in your root folder?
    Mine worked fine for OI9 but when I installed it to an OI10 folder, the utilities dll was deleted but not replaced.
    For me that means I don't get to test the super string because I fail upon opening the app with a different function call missing.
  • AusMarkBAusMarkB
    edited December 18
    If I manually add a utilities.dll that I believe should work, my about details show me this, so, clearly I'm missing something in ten.

    Where is the editor Version drawn from?
  • MattCrozierMattCrozier
    Yes, the SRP Editor installer replaced SRPutilities.dll with the new version, 2.2.11.6. That seems ok.

    It looks like SYSOBJ/$SRP_EDITOR_SERVICES is missing from the SRP Editor RDK for OI10. It's there in the OI9 RDK.
  • KevinFournierKevinFournier
    Try downloading the installer from the website and try again. It'll be version 3.4.6.12, and it should have the missing entity. Not sure how that one slipped through our trials.
  • Chris_MeyerChris_Meyer
    After applying the latest editor, utilities & controls I now have the status bar on the MDI showing half the data. The status bar is too low.


  • DonBakkeDonBakke
    Chris - Is the SRP Editor maximized and still looking like that? If so, do other apps appear normal when maximized? Your taskbar seems a bit tall to me. Also, if you used the most recent installer Kevin posted then the versions should be 3.4.6.12.
  • Chris_MeyerChris_Meyer
    Updated the editor to the latest and still have the issue. Other apps (word & Excel)are displaying the task bar correctly

  • AusMarkBAusMarkB
    edited December 18
    I just installed the latest and brought my controls up to date as well. I was using an older version of srpcontrols.ocx.

    I now have the same symptoms Chris just reported

    The statusbar is the app's mdi, not the editor. The two may or may not be related as I updated both the editor and the controls before testing.
    It may be a ribbon control thing.

    Controls is now 4.2.6.8. It was on about 4.1.14
  • DonBakkeDonBakke
    The statusbar is the app's mdi, not the editor. The two may or may not be related as I updated both the editor and the controls before testing.

    If so, then this would have been good to note straight away. Please confirm (especially you Chris) and then perhaps move the issue to the Ribbon control forum.
  • Opto_WillOpto_Will
    I just updtated the SRP suite as well and at first glance, no cosmetic issues.

    If you were on a old version of the Controls, maybe they predated the use of LayoutChildControl (v 4.2.2 I think)?

    For OI 9.4.6, I had to add some code (as per Kevin's notes) to a localised version of the FW_MAIN_EVENTS Create (right before the frame is set to Visible) to use Kevin's 'new' LayoutChildControl method for the Ribbon Control.

    That sorted out a LOT of my issues in this space regarding the statusbar.
    There is a thread in the Ribbon Control forum that has some code samples.
  • AusMarkBAusMarkB
    I recall the conversation.
    I wasn't experiencing the issue at the time, so I just let it slide and thought it had been addressed.
    I have no reference to the layoutchildcontrol method in the app, so I guess everyone let it slide. :D
  • KevinFournierKevinFournier
    SRP Editor 3.4.7 just released.
  • MattCrozierMattCrozier
    Just sayin' - the installer pages still say 3.4.6 - not a major ;)
  • BarryStevensBarryStevens
    edited December 18
    OI10.2.3 (b2) (OI9 appears OK) All compiles are comming up with suspected unassigned variables that are not.
  • MattCrozierMattCrozier
    All compiles are comming up with suspected unassigned variables that are not

    Not for me. There must be specific circumstances..
  • BarryStevensBarryStevens
    edited December 18
    Ok, found one that you should be able to compile.
    @MattCrozier what do you get?

    Compile Function Age_Invoice(Inv.Date, Age_Date, Type) ** to age the invoice according to invoice date and no of days/months Declare Function Unassigned If Unassigned(Type) Then Type = 'DEBTOR' If Unassigned(Age_Date) Then Age_Date = Date() Age.Period = '' If Type = "DEBTOR" then Gosub AgeDInvoice End Else Gosub AgeCInvoice End Return Age.Period ************ AgeDInvoice: ************ DEBTORS.AGING.PERIOD = XLATE('GROUP_MASTER',0,37,'X') IF DEBTORS.AGING.PERIOD = 'M' THEN REP.MTH = Field(Oconv(Age_Date,'D/E'),'/',2) INV.MTH = FIELD(OCONV(INV.DATE,'D/E'),'/',2) DAYS.OS = Age_Date - INV.DATE IF DAYS.OS > 91 THEN AGE.PERIOD = 4 END ELSE MTH.OS = REP.MTH - INV.MTH IF DAYS.OS < 0 THEN MTH.OS = 0 IF MTH.OS < 0 THEN MTH.OS += 12 BEGIN CASE CASE MTH.OS = 0 ; AGE.PERIOD = 1 Case MTH.OS = 1 ; AGE.PERIOD = 2 CASE MTH.OS = 2 ; AGE.PERIOD = 3 CASE MTH.OS > 2 ; AGE.PERIOD = 4 END CASE END END ELSE *process weekly aging AGE.PERIOD = INT((Age_Date-INV.DATE)/7)+1;*number of weeks IF AGE.PERIOD > 4 THEN AGE.PERIOD = 4 END IF AGE.PERIOD < 1 THEN AGE.PERIOD = 1 Return ************ AgeCInvoice: ************ REP.MTH = Field(Oconv(Age_Date,'D/E'),'/',2) INV.MTH = FIELD(OCONV(INV.DATE,'D/E'),'/',2) DAYS.OS = Age_Date - INV.DATE IF DAYS.OS > 91 THEN AGE.PERIOD = 4 END ELSE MTH.OS = REP.MTH - INV.MTH IF DAYS.OS < 0 THEN MTH.OS = 0 IF MTH.OS < 0 THEN MTH.OS += 12 BEGIN CASE CASE MTH.OS = 0 ; AGE.PERIOD = 1 Case MTH.OS = 1 ; AGE.PERIOD = 2 CASE MTH.OS = 2 ; AGE.PERIOD = 3 CASE MTH.OS > 2 ; AGE.PERIOD = 4 END CASE END Return

    This is what I get:

  • MattCrozierMattCrozier
    That compiles with no errors for me..
  • BarryStevensBarryStevens
    Sorry, but you are definately 3.4.7.1 ?
    What OI10 version?
  • MattCrozierMattCrozier
    OI10.2.3.20794
    SRP Editor 3.4.7.1
  • BarryStevensBarryStevens
    edited December 19
    @KevinFournier

    looks like this issue was back in 3.4.6 as well.

    Correction, not ALL compiles give an error.

    Do you have any clues as to what the reason might be?

    Note line numbers are correct in the editor (the paste added a blank on line 1.
  • MattCrozierMattCrozier
    Have you tried compiling this in OI's editor? If the same thing happens there then it's probably not specifically an SRP Editor thing..
  • BarryStevensBarryStevens
    First thing I did. Clean compile
  • BarryStevensBarryStevens
    edited December 18
    deleted
  • KevinFournierKevinFournier
    edited December 19
    I copied your code into both OI 9 and OI 10.2.3 and it compiled without VNAV errors. I made sure that no VNAV filtering options were checked in the Options. Keep in mind that SRP Editor does not do any VNAV checking on it's own. It calls OI's BLINT and then filters out false positives (if the settings are active).
  • BarryStevensBarryStevens
    Was that beta 2 of 10.2.3?
  • KevinFournierKevinFournier
    Yes
  • BarryStevensBarryStevens
    Can you do me a favour and add this code after the 'Compile function......'
    declare function Get_Property
    VersionSystem = Get_Property("SYSTEM", "VERSION")

    and see if you get a vnav compile error on VersionSystem.

    Just in case this gives you a clue - I disabled the vnav checking in the options and I still get vnav warnings (reopened the editor)
  • MattCrozierMattCrozier
    No problem there.

    If you include a #pragma output statement, does this show any difference in what's actually being compiled?
  • BarryStevensBarryStevens
    No diffence.
    Created a clean install of 10.2.3 - no issue.

    So, I now need to do a bit of detective work.
    I had previously in this process updated a clean release 10.2.3 with beta 2 and using EXAMPLES compiled that code no errors. Then ran my dev copy of OI (not the app run) , then swithech back to the clean copy, compiled ok, then added those 2 lines of code and got the vnanv issue.

    I then overwrote the clean upgraded copy with a full install of beta 2 now cant get the last 2 lines added vnav issue.

    I will now try upgrading the clean with the upgrade.
    then depending on results:
    Re-upgrading my dev copy with the issue.
  • KevinFournierKevinFournier
    I added the suggested lines of code in 10.2.3 Beta 2 and still did not get a VNAV error.
Sign In or Register to comment.