Re: Workgroup file information file error: OleDB to Access file
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 01/31/05
- Next message: NuTcAsE: "Re: Lookup table in separate database"
- Previous message: NuTcAsE: "Re: Inserting records into Multiple Tables in Dataset and Database (C#)"
- In reply to: Paul Keister: "Re: Workgroup file information file error: OleDB to Access file"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 12:04:40 -0600
On Mon, 31 Jan 2005 07:46:45 -0800, "Paul Keister" <bogus_info_bogus@bogus_pjpm.biz> wrote:
¤ "Paul Clement" <UseAdddressAtEndofMessage@swspectrum.com> wrote in message
¤ news:pqgsv0psnfa9cnv8rj67ded11evj9oks0l@4ax.com...
¤ >
¤ > Any chance the files are read-only or you don't have the appropriate
¤ > permissions to open the
¤ > database? I'm assuming that this is a VB.NET app and not an ASP.NET app.
¤ >
¤ >
¤ > Paul ~~~ pclement@ameritech.net
¤ > Microsoft MVP (Visual Basic)
¤
¤ Yes, this is a .NET app, not and ASP.NET app. It's actually C#.NET. This
¤ is a good thought, but this was not the problem. Here's what's wrong:
¤ there's a typo in the connection string. It should be, "OLEDB:System
¤ Database," not, "OLE DB:System Database." Doah!
¤
¤ I'm glad nobody noticed this. I feel dumb enough already. This is further
¤ confirmation of one of my long-standing theories: the worst bugs are caused
¤ by the dumbest mistakes. In other words, if you find yourself spending
¤ hours on a problem, don't look for subtle explanations, look for glaring
¤ errors!
¤
I have to admit I missed it too and syntax was the first thing I looked for. ;-)
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
- Next message: NuTcAsE: "Re: Lookup table in separate database"
- Previous message: NuTcAsE: "Re: Inserting records into Multiple Tables in Dataset and Database (C#)"
- In reply to: Paul Keister: "Re: Workgroup file information file error: OleDB to Access file"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|