Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Catastrophic failure Run-time error '-2147418113'

Status
Not open for further replies.

JerryKlmns

IS-IT--Management
Feb 7, 2005
2,062
GR
Catastrophic failure ----> Catastrophic problem

On a Pc with MDAC 2.1 and on another with MDAC 2.6, the following line produces this error.
Code:
Currentproject.Connection.Execute "Insert Into Sbc1 Select Sbc.* From Sbc;", adExecuteNoRecords, adCmdText

after a litle search around and based on what is said here, I created a NewConnection with
NewConnection.CursorLocation = adUseClient
with no luck.

Checking the errors produced, I have found that this comes from (Err.Source=) the Provider(=Microsoft.Jet.OLEDB.4.0), no Err.SQLState given, and Err.NativeError=-2147418113 = Err.Number
Given that there is a PK on Sbc1 table, after the error, DCount("Type", "Sbc1") returned 0. I re-executed the line and a duplicate error message come up and DCount("Type", "Sbc1") still 0!

That line of code was working properly till yesterday. Table Sbc is a linked table of a txt file (using schema.ini). The txt file is in proper format and doesn't contain any garbage data. No change on schema.ini file. The only new is that the database used is stored on a compressed drive (OS WinNT4.0 sp6). It is stored there empty and copied to local drive C:\ where it is operated (OS WinNT4.0 sp6).The txt file and schema.ini are both stored there and copied to local drive C:\ for use.

Although the code mentioned is working properly using MDAC2.7 (we'll upgrade all PCs) I don't think the version of MDAC is the real problem.

Any opinion or suggestion is welcomed.[banghead] [bomb][hammer]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top