|
Hi
Julie,
Sounds
very odd. Is there anything odd about the name you have used for your new
database? Can you provide a set of Full Debug logs showing the error occuring
(see Tools -> Options for the log settings) please?
Regards, Dave.
I'm using PgMigration to migrate three DBF files
to my PostgreSql Development server. This was working fine until I made one
eensy teeny change.
Some background: I am in the process of moving
all of my data from a PostgreSql 7.2.X server to a PostgreSql 7.3.X server on
another machine. On the new machine I created a database with the same name as
the database on the old machine then I loaded the dumped sql file. Everything
worked fine.
The change. We needed to change the name of the
database so I created a new database with a new name. I then loaded the dumped
sql file from the database with the old now. Now I cannot use PgMigration to
load DBF files. I select dBase files as the ODBC database type. As soon as I
select next I get the following message:
Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done.
Below is what Microsoft says is the cause and the
solution. Any help would be greatly appreciated. I am on the last step
(writing up the user documentation) of the project at the last hour (actually
last 1.5 hours) and I need to have this project out the door. If the only easy
solution is to put the name back as it was, I can live with it but my boss
won't be happy.
Thanks in Advance.
Julie
CAUSEThe following are two possible causes of this error:
- In the registry, under the key for an OLE DB provider's CLSID, there may
be an entry named OLEDB_SERVICES. If the OLE DB provider being used to make
the ADO connection doesn't have the OLEDB_SERVICES entry, and ADO tries to
set up a property that is not supported by the provider, the error occurs.
For more information on this registry entry, see the "Resolution" section.
- If OLEDB_SERVICES entry exists but there is a problem in the ADO
connection string, the error occurs.
If the OLEDB_SERVICES registry
entry is not present, the call to set up a property is made directly to the
provider. If the provider does not support the property, the
SetProperties OLE DB call made by ADO will fail. This is a
fatal failure if the property is required in order to make a connection. If
the property was explicitly included in the connection string, it is most
likely required. If the property setting is optional, the failure is
not fatal. This is the case when you connect without explicitly setting the
property in the connection string. In this case, ADO sets the property to True
but marks it as optional.
RESOLUTIONYou can work around this problem in the following ways:
|
