As expected, it doesn't work with SQL 6.5.
However, the error/exception should be handled instead of throwing a .Net exception error, perhaps a helpful explanation that such server should be added to the list of "do not use".

Thanks!
jreynolds
0

Comments

3 comments

  • Lionel
    Thankyou for reporting this problem I have put in our bug tracking system. Should get fixed in the patch release.

    Lionel
    Lionel
    0
  • Bart Read
    Hi there,


    Could you send us the contents of the error dialog please so that we know where to look for this as there are any number of places it could go wrong?


    Thanks,
    Bart
    Bart Read
    0
  • Bart Read
    Hi there,


    This error should be handled better in SQL Prompt 3.1. You can download an early access release by following the instructions here:

    http://www.red-gate.com/MessageBoard/vi ... php?t=4487

    Hope that helps.


    Thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.