This topic is locked

issue when opening old projects after DSN has changed

5/24/2007 4:53:55 PM
ASPRunnerPro General questions
B
brasil author

let me see if i can explain this problem:

  1. i created a finished project in v4.1 with a DSN that points to a certain server. everything works perfectly
  2. i moved the whole project to a different server and modified the DSN info in dbconnection.asp without going through ASPRunner
  3. later, when i try to open the project in ASPRunner it gives me two errors because it can't find the system DSN it's expecting.
    The Problem:

    after i enter the new system DSN after closing the error alerts i have lost most or all of my project settings and have to start all over again!
    The Workaround:

    i went back to my saved .aspr project file, opened it in notepad, and corrected this line: <m_strConnectionString>. when i opened it with the correct DSN, my project settings were preserved.
    The Suggested Fix:

    when opening a project after the DSN has changed, there should be a friendly alert saying the program can no longer find the original DSN and offering the user a chance to point to the new one before losing all of the original project's settings.

Sergey Kornilov admin 5/25/2007

Actually ASPRunnerPro supposed to do exactly what you said.

I'll double check this.