Re: Vista Migration

Tech-Archive recommends: Fix windows errors by optimizing your registry


"John" <XMS@xxxxxxxxxxxxxxxxx> wrote in message
news:33691E03-3F60-4A31-AE3A-04B1F33D2AA1@xxxxxxxxxxxxxxxx
This is old code. I've written almost none of it. My assignment is to
move
it to Vista spending as little time on it as possible. You can guess how
well a rewrite will sell.

Pretty sure I have the necessary rights, although with Vista you can't
take
that as a given. I'm the only person touching the MDB, so locking is not
likely to be an issue.

I'm hoping that this is something others have seen before. An explanation
of
why the change would be nice, but I know better than to hold my breath
over
that.

Thanks for the reply,

John

<snipped>

I have seen it before and the reasons I gave you are the most common causes
for this error.

File/Folder permissions.
A locked database.
DSNs.

The permissions issue is easy enough to check, open the folder and check for
all rights for everyone, and no .ldb file. But definitely check it.

Also don't assume "you" are the only one touching the database. In this
context it isn't "you" that is important, it's your app/s, and it is quite
possible for an App/s to actually be accessing a database with more than one
"dsn" or connection.

The third cause, since you are using ODBC, comes about because of
configuration problems on the target box. If specifically using a DSN (ODBC
Manager) one often finds that they have to replace a File DSN with a System
DSN, for example. Occasionally ODBC doesn't get configured correctly in the
Registry. Some other install may have replaced the "MSDASQL.1" driver with
something else, or ODBCINIT entry might even be missing. Any of a host of
possiblities.

For that, to preserve your sanity, you will have to play around a bit.
Create a minimal application that uses your connection string. Then use the
ODBC Manager to create a DSN that does work. Then go from there. (At some
point you can skip the actual DSN, but you have to find a working
configuration first in order to test the intalled components and ODBC
services.)

But rest assured a simple switch, toggle, or click somewhere will resolve
the problem. It is the classic - "A day to find, a minute to fix". <g>

Also take a closer look at what Mr. Wang is telling you. (He knows what he
is talking about.) Converting to ADO means only changing the connection
string. Something that may be necessary even if you stay with ODBC.

I appreciate your problem with the pointy-haired ones. Have been there, done
that.
It may help to show them that by using ODBC with the ADO access data library
they are in effect adding an extra layer to process. An extra layer of
performance hits and as you discovered, an extra layer of configuration
issues.

[IMHO, by proclaiming by edict that a migration to Vista is to be done "with
out spending any time on it", demonstrates that your bosses are complete
idiots. "Connection" issues are only the first round. <g>]

-ralph




.

Relevant Pages

  • Re: VFP and DSN questions
    ... Do I have to use DSN? ... Which connection string? ... But ODBC will be the simplest. ... The DSN is a specific configuration of the ODBC layer (defines whatr ...
    (comp.lang.php)
  • Re: Word 2000/2002 - Proper Mail Merge steps for ODBC?
    ... > Document to connect to a Secured Access Database, ... using the ODBC provider for OLEDB. ... they have a .dsn extension. ... directly (in the Open/Select Data Source dialog box). ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Vista compatibility problems with Word 2000 mailmerge
    ... If you are starting from a new Vista installation, the thing most likely to be missing on your system is the ODBC DSNs that your Word documents expect to find. ... Unfortunately, because you cannot open a WOrd Mail Merge Main Document unless the data source is present, it is sometimes impossible to discover what the data source used to be. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Silly ODBC Connection problem
    ... it seems to me this must be done interactively on each client--either that or use the magical "DSN-less" connection. ... It's been 11 or years or so since I wrote about ODBC so it's getting kinda fuzzy. ... 556-9205 (Pacific time) ... > created a System DSN named "MyDSN" in the ODBC Administrator tool. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Beginner: How do I link via ODBC from a PC into an AS400?
    ... Options, Miscellaneous, How to keep Microsoft Office Documents Protected, ... The moment I select ODBC Databases from Files of Type, ... I have added a User DSN based on the Client Access Driver, ...
    (microsoft.public.access.externaldata)