How Entertaining! [modified]

[Roger Wright]

I've spent the last three hours trying to create a new connection to an Access file in Server Explorer, following the guidance in VS2008 Help. Nothing works. But out of sheer frustration I clicked on Test Connection with the Connection String box blank. It passed. Apparently Test Connection does absolutely nothing, so I can stop wasting my time clicking on it. Clicking on OK tells me that the "Format of the initialization string does not conform to specification starting at index 0" which makes perfect sense to me. Apparently it's just as clear to Microsoft, as when I search on the error message it returns 0 responses. I guess they never tried connecting to an Access DB with VS2008... Crap! I'm so tired of Microsoft making simple tasks impossible! I've got a simple mdb file from work with meter readings from a now defunct reading system. All I wanted to do was load and display two or three columns from one table in the file, and print them so the accountant can enter the readings into the billing system. I thought this would take about two hours - based on past experience doing very similar things. This was easier using DOS and Paradox! For the record, I searched on Creating a New Connection in Server Explorer, located the connection string for Access in the resulting example, copied and pasted it into the wizard, and changed the file path to match my database file. There were several results, and I tried them all. Nothing worked, except the error message Microsoft doesn't recognize. How do you folks do this for a living? Hard drugs? Alcohol in vast quantities? I did some more searching, with no positive results. But I did manage to find a link to provide Microsoft with some feedback, to wit: I found the following step to be confusing: 1. In the Database file name box, enter the path to the .mdb file, or click the Browse button to locate the database file. There is no such box in VS2008, just a Connection String request that offers no clues. Using the connection string examples provided by MSDN, with appropriate modifications to point to the path of my Access database, did not help. By the way, if I Test Connection using a blank connection string, it passes, but clicking OK results in the entirely worthless message, “Format of the initialization string does not conform to specification starting at index 0.” Utterly useless, as always. Thanks for being consistent, if not useful. Over the past 20+ years I’ve been setting lower expectations for Microsoft assistance, and you’ve

[_Damian S_]

Roger Wright wrote:

How do you folks do this for a living? Hard drugs? Alcohol in vast quantities?

Yes... and a good deal of self loathing!!

I don't have ADHD, I have ADOS... Attention Deficit oooh SHINY!! If you like cars, check out the Booger Mobile blog | If you feel generous - make a donation to Camp Quality!!

[riced]

Roger Wright wrote:

All I wanted to do was load and display two or three columns from one table in the file, and print them so the accountant can enter the readings into the billing system.

Why use VS? If you have the mdb chances are you have Access, so just open open Access, use the mdb, create a report and run it. :)

Regards David R --------------------------------------------------------------- "Every program eventually becomes rococo, and then rubble." - Alan Perlis The only valid measurement of code quality: WTFs/minute.

[PIEBALDconsult]

Roger Wright wrote:

Server Explorer

What's that? Never heard of it.

Roger Wright wrote:

connecting to an Access DB with VS2008...

Whatever for? That's for writing code, not for doing database work. Generally, when I am trying to determine a connection string for some new database, I use a UDL file.

[Roger Wright]

The laptop I need to use for meter reading, and exporting data, doesn't have Access installed, and no one wants to spend the money on buying a copy. But you're right, that would be the sensible solution.

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[Roger Wright]

PIEBALDconsult wrote:

I use a UDL file.

Never heard of it, but I'll look it up. In actuality, I'm used to coding db stuff manually, and that's all I really understand, but I thought I'd try out the new toys in VS. Note to self: Never put your faith in Wizards.

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[riced]

Here's a thought - could you use OpenOffice? It has a database component which I've not used so I'm taking a guess. But it is free. :)

Regards David R --------------------------------------------------------------- "Every program eventually becomes rococo, and then rubble." - Alan Perlis The only valid measurement of code quality: WTFs/minute.

[Lost User]

PIEBALDconsult wrote:

when I am trying to determine a connection string for some new database, I use a UDL file.

Then you sound just the person to answer this[^] question.

It's time for a new signature.

[PIEBALDconsult]

Or maybe not... I only use the UDL file to get the connection string -- then I do other things with it.

[PIEBALDconsult]

Roger Wright wrote:

new toys

X| Stick with what works.

[The Man from U N C L E]

I have a .Net app that uses access as a database and I use the following connection string with no problems. "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\mydatabase.mdb;Jet OLEDB:Database Password=password;" You could also check out http://www.connectionstrings.com/access[^].

If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles]  [My Website]

[Roger Wright]

I did tonight, and hand coding the connection string - identical to that used in the wizard - worked perfectly, first try. :-D

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[Roger Wright]

The problem is in the Add Connection wizard, not the connection string. The same string that yields the completely incomprehensible error message when used with the wizard works perfectly when hand-coded in the app. I'll stick with the old fashioned way of doing connections from now on. :-D

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[The Man from U N C L E]

Just came across this post on the VB Developer Center. Add Connection Wizard Fails[^] It sounds like the installation of the Access data provider is a bit dodgy. They suggest the following, and it apparently works a treet. 1) Run regedit.exe; 2) Browse to the location "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" in the tree; 3) If there is a child node in the tree called "ProgID", then you are experiencing a different problem. Otherwise, follow these steps to modify the registry: 1) Right click the node and select "New > Key"; 2) Enter "ProgID" as the name; 3) Go to the main window and double click "(Default)"; 4) Enter the value "MSIDXS.1"; Now if you run Visual Studio, it should be working. Hope this helps.

If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles]  [My Website]

[Roger Wright]

Now this is interesting... I have Visual Studio 2008 Express installed at work, and the registry settings are already exactly what you've described. It works perfectly, using the same database I'm trying to connect to at home. What's odd is that, my home installation is VS 2008 Standard, and the connection wizard dialog box is entirely different! No Browse button, to start with, and of course I never get past that point to see the rest. I'll check these registry settings as soon as I get home; this might just do the trick!

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[Roger Wright]

That worked a treat! What an obscure fix for a non-obvious problem! Even worse, this source came from a VS2005 post; why is it still a problem in VS2008?:mad:

"A Journey of a Thousand Rest Stops Begins with a Single Movement"

[The Man from U N C L E]

Glad I could help.

If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles]  [My Website]