RE: WinXP behaves Different than Win2000 on Network ODBC connectio
From: Morris (Morris_at_online.nospam)
Date: 02/25/05
- Next message: VN: "RE: dbo. records cannot be modified."
- Previous message: SeanMcElroy66: "Re: Sage Accounts-ODBC-[42000] Invalid Table Specification"
- In reply to: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Next in thread: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Reply: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 19:27:02 -0800
I tried changing the registry setting for the DSN to use a UNC and I tried a
FIle DSN with a UNC neither one worked.
How is WinXP and Win2000 different in this matter that one would work and
the other not? In a test environment we reproduce the behavior but do not
even get a provider error as we do at the live site, which I posted
previuosly in this thread.
Any direction here would be appreciated.
Morris
"Kevin Yu [MSFT]" wrote:
> Hi Morris,
>
> Please refer to the following link for more information.
>
> http://support.microsoft.com/?id=165866
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
>
- Next message: VN: "RE: dbo. records cannot be modified."
- Previous message: SeanMcElroy66: "Re: Sage Accounts-ODBC-[42000] Invalid Table Specification"
- In reply to: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Next in thread: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Reply: Kevin Yu [MSFT]: "RE: WinXP behaves Different than Win2000 on Network ODBC connectio"
- Messages sorted by: [ date ] [ thread ]