Problem With Old Apex

Discussion in 'a la mode (TOTAL)' started by john marcinik, May 24, 2005.

Thread Status:
Not open for further replies.
  1. john marcinik

    john marcinik New Member

    0
    Apr 13, 2004
    Professional Status:
    Certified Residential Appraiser
    State:
    Maryland
    I'm having problems with old apex.
    I have to constantly hit save or F2 to not lose data.
    This is especially true when I clone a report.
    Anyone else having problems?
    Of course you must realize I'm a cheap +++++ and won't upgrade to Apex 3.

    Thanks
     
  2. Joker

    Joker Elite Member

    0
    May 28, 2002
    Professional Status:
    Certified General Appraiser
    State:
    Ohio
    I've had that problem. I did upgrade to Apex 3, but tried Apex 2 first (apparently I paid for it a few years back but didn't know it). After using Apex 2, I switched back to Winsketch. I've never had a problem with it and can sketch in half the time with Winsketch vs. Apex. I don't even wanna think about Apex 3.
     
  3. Scott Kibler

    Scott Kibler Elite Member

    7
    Oct 7, 2003
    Professional Status:
    Certified Residential Appraiser
    State:
    Illinois
    :lol: I knew Joker was jealous of me.

    I noticed an issue too.

    If I complete a sketch and save, then go back to edit it later, the changes don't want to transfer to the report. I found exiting out of wintotal then going back in and opening the file usually works.

    I figured this was part of the upcoming incompatibility issue that Alamode was talking about when they rolled out Apex 3.0. I assume it will become worse when Aurora hits the streets

    Having made a public stink about Apex 3.0 some months ago, a wierd sense of pride is keeping me from upgrading...just yet. ;)
     
  4. Joker

    Joker Elite Member

    0
    May 28, 2002
    Professional Status:
    Certified General Appraiser
    State:
    Ohio
    You're my idol, skibs. I wanna be just like you when I grow up.
     
  5. Jim Bearden

    Jim Bearden Member

    0
    Feb 24, 2003
    Professional Status:
    Certified General Appraiser
    State:
    Colorado
    It is amazing what a call to ala mode will reveal.
     
  6. john marcinik

    john marcinik New Member

    0
    Apr 13, 2004
    Professional Status:
    Certified Residential Appraiser
    State:
    Maryland
  7. john marcinik

    john marcinik New Member

    0
    Apr 13, 2004
    Professional Status:
    Certified Residential Appraiser
    State:
    Maryland
    Ala mode told me that when they figure it out they will send out an update.
    There is a problem with microsoft updates and Apex.
     
  8. Proactive

    Proactive Senior Member

    9
    Jan 15, 2002
    Professional Status:
    Certified Residential Appraiser
    State:
    Washington
    This is what ala mode tech support told me as well. I have had the same problem (using Apex IV) since the first week in April.

    I am considering biting the bullet and upgrading to Apex 3.0. There is a $100 off coupon that ala mode has out (good through this Friday) that would help soften the blow.

    Is anyone using Apex 3.0 having this same sketch saving issue? I'd hate to upgrade only to continue to have the same problem... :unsure:
     
  9. john marcinik

    john marcinik New Member

    0
    Apr 13, 2004
    Professional Status:
    Certified Residential Appraiser
    State:
    Maryland
    The Tech told me the same problem applies with Apex 3.0.
    I don't know for sure. I don't have it.
     
  10. Robert Smoote

    Robert Smoote Junior Member

    0
    Dec 10, 2004
    Professional Status:
    IT Professional-Appraisal Related
    State:
    Texas
    Good Morning All:

    First of all, thank you for posting. While it's no fun reading about problems our software is having/causing/etc. - it's extremely helpful in pointing us in the right direction for improvement.

    Second, I apologize for any inconvenience this has caused you.

    Yes, there was a problem with integration opf Apex v2.x and WinTotal which happens with a Critical Update in the XP OS (May time frame). The latest on this was we were finally able to duplicate this problem on our end and preliminary testing shows that this problem appears to be resolved.

    However, if this continue to be a problem for you, a simple work-around would be to manually Save the file and then close Apex before going back to WinTotal.

    Unfortunately, with the v2.x product being as "old" as it is now (4+ years) it becomes more vulnerable to the everchanging Operating System environments and new technologies.

    BTW - This problem does not exist in Apex v3, which was written with the latest tools designed to address recent and current environments.

    Hope this helps! Please continue to let us knwo about any problems you are experiencing with our software. Chances are, others are having problems too and it gives us the feedback necessary to correct them.

    Have a great day!
     
Thread Status:
Not open for further replies.

Share This Page