 |
 |

01-16-2004, 07:40 AM
|
|
Newcomer
|
|
Join Date: Aug 2003
Posts: 4
|
|
Method ~ of Object ~ Failed
|
Ok, Here is a question for all of you VB Experts:
I am using VB 6.0 SP5. I have a DLL written in VB that generates an Excel spreadsheet using automation. In this case, it is a spreadsheet for a Parts Requisition. When I create a new parts requisition and generate the spreadsheet, there is no problem. When I exit the dialog box and edit the same requsition and try to generate it again, then I get the above error.
This problem only happens when I run the front end application in the VB IDE. It does NOT happen if I run the DLL in a separate VB session to try to debug it. It also does not happen if I compile the front end into an executable and run the executable. It only occurs if the front end is being ran in a single VB session.
Since it does not occur in the Exe, that makes it not so important, but I would still like to know why it is happening and what fix there is for it.
Thanks.
|
|

01-17-2004, 03:25 AM
|
 |
Licensed to post
* Expert *
|
|
Join Date: Jul 2003
Location: York, Uk
Posts: 1,637
|
|
|
What line of code is giving this error:
Method ~ of Object ~ Failed
?
|
|

01-17-2004, 07:16 AM
|
 |
Lost Soul
Super Moderator * Guru *
|
|
Join Date: May 2001
Location: Vorlon
Posts: 18,887
|
|
|

01-19-2004, 07:38 AM
|
|
Newcomer
|
|
Join Date: Aug 2003
Posts: 4
|
|
Still a Problem
|
Hello:
The problem that I mentioned has not been resolved. Here is some additional information:
The problem does not occur when I run the DLL in a second instance of VB, thus I cannot tell what line of the program the problem occurs in. It only occurs when I run the application (the front end) in a single instance of VB.
I have upgraded to Visual Studio 6.0 SP5, and the problem still occurs.
Unlike the other users who complained about a similiar issue, I am not running two instances of VB when the problem happens. In fact, if I run two instances of VB (the front end in one, and the back end DLL in another), the problem does not occur.
I am not using any templates in the Excel spreadsheet. I am just creating a new workbook and writing directly to the cells of the spreadsheet.
So, can anyone tell me why this is happening??
|
|

01-19-2004, 08:03 AM
|
|
Freshman
|
|
Join Date: Jul 2003
Posts: 46
|
|
I think MDAC installation is necessary...
Quote: Originally Posted by Brian149 Ok, Here is a question for all of you VB Experts:
I am using VB 6.0 SP5. I have a DLL written in VB that generates an Excel spreadsheet using automation. In this case, it is a spreadsheet for a Parts Requisition. When I create a new parts requisition and generate the spreadsheet, there is no problem. When I exit the dialog box and edit the same requsition and try to generate it again, then I get the above error.
This problem only happens when I run the front end application in the VB IDE. It does NOT happen if I run the DLL in a separate VB session to try to debug it. It also does not happen if I compile the front end into an executable and run the executable. It only occurs if the front end is being ran in a single VB session.
Since it does not occur in the Exe, that makes it not so important, but I would still like to know why it is happening and what fix there is for it.
Thanks.
|
|

01-19-2004, 07:40 PM
|
|
Newcomer
|
|
Join Date: Aug 2003
Posts: 4
|
|
I already reinstalled MDAC 2.6 RTM from the Microsoft web-site. I have used their component checker application and my files now match exactly with MDAC 2.6 RTM. It did not help.
Quote: Originally Posted by dincer80 I think MDAC installation is necessary...
Quote: Originally Posted by Brian149 Ok, Here is a question for all of you VB Experts:
I am using VB 6.0 SP5. I have a DLL written in VB that generates an Excel spreadsheet using automation. In this case, it is a spreadsheet for a Parts Requisition. When I create a new parts requisition and generate the spreadsheet, there is no problem. When I exit the dialog box and edit the same requsition and try to generate it again, then I get the above error.
This problem only happens when I run the front end application in the VB IDE. It does NOT happen if I run the DLL in a separate VB session to try to debug it. It also does not happen if I compile the front end into an executable and run the executable. It only occurs if the front end is being ran in a single VB session.
Since it does not occur in the Exe, that makes it not so important, but I would still like to know why it is happening and what fix there is for it.
Thanks.
|
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
|
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|
|
|
|
 |
|