About 3219 or -2147217887
Hello Everyone,
I did a vb6 program. it run normal in my computer. but im customer computer, It gave errors,"Operation is not
allow in this context.3219 Or "Multiple-step operations generated errors. Check each status value.-2147217887.
I use PDW to make setup file. incuded any file except msado.tlb because it always give me error meassage when I install program.
Is it the problem of msado.tlb? how can I include it in PDW without error?
Thanks in advance!
[500 byte] By [
whygh] at [2007-11-11 7:38:37]
# 1 Re: About 3219 or -2147217887
you forgot to mention which library/database/components are using.
The error can be data related. "Multiple-step operations generated errors" can come trying to insert into a table rows that contein illegal values.
Marco
mstraf at 2007-11-11 17:26:41 >
# 2 Re: About 3219 or -2147217887
thanks .
Sorry. Actually I donot know which code got an error message. I tried with the customer's data In my computer, everything is fine. I donot know how to deug this error in customer's computer.
My code as belowed is:
1. connect Foxpro database
Set conn = New ADODB.Connection
cnnstr = "SourceType=DBF;" _
& "SourceDB=" & App.Path & "\;" _
& "Driver={Microsoft Visual FoxPro Driver}"
conn.Open cnnstr
2.read the text document , convert into the foxpro table
3.retrieve this table, display the recordset on datagrid
4. After user confirms, generate text document from recordset
whygh at 2007-11-11 17:27:41 >
# 3 Re: About 3219 or -2147217887
Handling errors in VB is lame, but at least it is there and if it is used properly can give useful clues.
What I usually do is trying to keep the body of methods as small as possible (in case I break them in multiple methods). In each method I put an error handling clause "on error goto errLabel", and when I display the error message I add the name of the method the error is coming from. In this way at least I have a clue in which part of the code the error is coming, and from the error code usually I can guess where the error is. But we do not put errors in our code, do we :)
In your case, I would do a google search for part of your error string, adding FoxPro. Sorry, I can't say more than this, I never had that kind of error. Try to post this problem in the database forum and see if you have more luck there
Marco
mstraf at 2007-11-11 17:28:37 >
