Sage 100

 View Only

  • 1.  64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 08:35

    Have a 64-bit client who has been having the print screen close issue and I finally told them I'd install the fix. So far, I've only put it on the server, and that has caused issues with VisualCut.  I can access one of the Crystal reports used in VC and it runs fine in Crystal (there is a 32 bit and 64 bit special ODBC driver used by all of the reports used in VC that have the company code and login/password hard-coded). But in VC it is prompting for a login and telling me the password is wrong. It also had an original error about a "low level driver" and listed one of the odbc dlls, but I can't recreate that one to get a screen shot of it. (I mistakenly assumed (I know) that it would pop up each time, so didn't grab it the first time.).

    I've emailed Ido to see if he has any ideas. 



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------


  • 2.  RE: 64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 16:31

    So apparently the 32 bit SOMETHING must also get changed.  Visual Cut is a 32 bit program.  However, Ido also has DataLink Viewer, which is 32/64 bit and I'm testing tonight to see if running it via that works.  It previewed fine within VC, so fingers crossed.



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------



  • 3.  RE: 64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 16:34

    Running the VC "Repair" sometimes helps with errors.  (Right-click the MSI...).



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 4.  RE: 64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 16:38

    Ido was on the client's machine with me the whole time, so I am assuming what we did was the only resolution.... But the next time I run into it, I can try that first.

    What happened was if you tried to run them manually from within VC, the wrong ODBC connection showed up, then if you managed to get it changed to the correct one, it still wouldn't connect. (They are silent connections and it asked for a login and if you left it blank, error, filled it in with login and password, error.)



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------

    Original Message


  • 5.  RE: 64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 16:48

    Premium / SQL DSN's with trusted connections can ignore DSN overrides in command lines... but SQL authentication (and cached credentials) does work better.

    For Providex data always use fully silent DSN's, and never type in credentials when running a report in VC.  (That can cache settings that interfere with the silent DSN...).



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 6.  RE: 64 bit closign print screen fix - issue with VisualCut

    Posted 02-24-2025 16:56

    Yup, these were silent DSNs - which had been working beautifully until I installed the 64 bit fix yesterday on the server (where VC runs).  That's what was so weird - it asked for credentials even though it was a silent DSN.

    However, now that I'm thinking about that - one other place where I installed the fix had the issue in SAGE pop up where it asked for the login when running a report.  That did not happen here - worked fine in Sage.



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------

    Original Message


Related Content