"Justin" <(E-Mail Removed)> wrote in message
news:BD20E202-8CD6-475F-BF0A-(E-Mail Removed)...
> Nuts...
>
> I was hoping for a "Hey, knucklehead, just uncheck the 'Make DSNs no
> workie'
> box" type of answer... Guess I'm out of luck, huh?
>
> Of course, here's the funnest part of this: it's only happen on one
> workstation, and, of course, it happens to be the boss's computer.
> Nice...
>
> Thanks,
>
> Justin
>
> "Haggis" wrote:
>
>>
>>
>> "Justin" <(E-Mail Removed)> wrote in message
>> news:78E67F69-2270-494A-8ECC-(E-Mail Removed)...
>> >> which ODBC SQL driver version are you using ?
>> >
>> > Looks like 3.5.
>> >
>> >
>> >
>> > "Haggis" wrote:
>> >
>> >>
>> >>
>> >> "Justin" <(E-Mail Removed)> wrote in message
>> >> news:7114CB5F-2516-4212-9602-(E-Mail Removed)...
>> >> > Have a weird issues I'm hoping someone's seen before...
>> >> >
>> >> > I have one workstation (XP SP 2) that's having some issues creating
>> >> > new
>> >> > DSNs
>> >> > or editing existing ones through the GUI.
>> >> >
>> >> > If I try to create a new DSN, things look ok at first. I can choose
>> >> > the
>> >> > driver (SQL, in this case) and get the screen that asks for the name
>> >> > of
>> >> > the
>> >> > data source and the server. If I click Finish, I get the
>> >> > congratulations
>> >> > screen, just like I should. However, if I click "Test Connection,"
>> >> > the
>> >> > window just disappears and the DSN doesn't appear in the list. Same
>> >> > thing
>> >> > happens if I click Next two more times instead of clicking Finish.
>> >> >
>> >> > I get similar results when I try to edit an existing one. If you
>> >> > click
>> >> > Finish, the changes don't appear to get saved.
>> >> >
>> >> > I can get around some of this by editing the registry directly to
>> >> > create
>> >> > and
>> >> > edit the DSNs, but that's obviously not a solution for the user.
>> >> >
>> >> > Oh, and if I do create a new DSN manually in the registry, it
>> >> > doesn't
>> >> > appear
>> >> > in the list in the GUI right away. If, however, I try to create a
>> >> > new
>> >> > one
>> >> > with the name I entered in the reg key, I get a warning that says
>> >> > the
>> >> > name
>> >> > already exists and it suddenly reappears if I save the new
>> >> > connection....
>> >> >
>> >> > Anybody have any ideas?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Justin
>> >>
>> >> which ODBC SQL driver version are you using ?
>> >>
>> >>
>> >>
>> I had the same sort of problem using versions higher than 3.51.9 , so
>> that
>> is what I stuck with (I never did find a resolution for the problem)
>>
>> you try that :>
>>
>>
>>
heh heh , always the way :> as I said I never did get a resolution to my
problem ..it involved installing a different driver..
you could un-install and re-install ....are you logged in as a Admin on the
computer ?
alternately can you copy a working DSN from another computer to this one and
see it ? copy to > "C:\Program Files\Common Files\ODBC\Data Sources"
|
Similar Threads
