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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Visual Bill Builder Vbomp32 runtime error '3704'

Status
Not open for further replies.

logicskr

Technical User
Jul 30, 2005
28
US
PSQL 9 & 7.6.300c upgrade, now unable to open Visual Bill Builder on any company. I get Vbomp32 run-time error '3704' Operation is not allowed when the object is closed. Closing that error box brings up a blank greyed out Visual Bill of Material screen with the cursor in the first field, but unable to scroll any data using the advance record arrows. Everything else seems ok, even Product Structures. I tried Exact's resolution for Doc ID: 12.262.558, which ran fine apparently, but did not correct the problem. Any ideas?
 
From the Exact portal:

This message will appear if the Field, File, and Index DDF files are not in the screens directory. These files should be located in the DTUPDATE.ZIP file in the \MACOLA70\Default directory. You can also get the latest DDF files from the download section of the support site the file needed is DTUPDATE.ZIP it contains updated demo data and the DDF files that are needed. Once this file is downloaded you can extract only the DDF files needed from the file using WinZip.

Peter Shirley
 
I already tried that, but still the same error. Is there a plan B?
 
Hmmmm - is it possible that your DTUPDATE.ZIP is not the correct one for 7.6.300C or that the DDF's in the screens directory aren't correctly dated for 7.6.300C? Seems odd that the error is identical to the one that Exact's reporting so I'd look to make sure that the fix they suggest actually 'took'.

Peter Shirley
 
Reinstall macola on the workstation ? Perhaps a DLL or OCX has to be registered.
 
The DDFs I have work on another installation of 7.6.300C so apparently they are the correct version. My error is consistent on all my client workstations, so doesn't seem like it's a matter of the client install being incorrect or corrupt. Maybe Norton Antivirus wasn't disabled when the Hot Topic fix was run. I'll try it again with Norton definitely disabled, but I don't think that's really the cause. I'll post back the result.

Thanks
 
Well, I still have the same error message. I turned off all antivirus and antispyware software on the server and the workstation I am running the fix from. I verified that no other directory in the Macola root has a "DATA" type name except for the legitimate company data directories. I ran the fix again. I rebooted the server and workstation. No difference.....I replaced the Vbomp32.exe in the Macola root thinking maybe it had become corrupt. No difference. The error occurs in all companies and the Visual Menu Builder does work in all companies, which surprised me. I don't get it.....maybe I should be considering a registry entry that exists that shouldn't, but I don't know what I would be looking for in the registry. Is there a dll file it needs that I should try to manually register? I'm running pretty thin on ideas about now.
 
I found this on the Macola portal, not related to visual bill builder but the exact same error message:

This error is typically caused by the lack of a valid demo data directory. For Workflow to successfully launch there are several minimum requirements related to the demo data directory that must be met. These are:

1) A demo data directory - with a valid naming convention of data_00
2) sql ddf's in the demo data directory
3) A compfile.btr (Company File) in the demo data directory

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Dgillz,
great point. I was going to type it last time, then decided to remove my diatribe. Short point, several times over the year I have had accounts that are "space conscious" and delete the electronics company, and later have bugs in the normal operation of the software.
 
Ok, still working on resolving this issue. I have found that all works in 7.6.300c with the 8.5 engine, but installing the 9.1 engine breaks things for Visual Bill Builder. Upgrading to 7.6 400a is no better or even going to the 9.5 engine (directly from Pervasive). Exact support hasn't been able to figure this one out either. I ran a couple of ODBC traces and I see Vbomp32 errors involving old Intersolv drivers, but I'm not sure I understand the log very well so maybe they are irrelevant, support doesn't seem to be interested in them. I've been told a number of things such as it being a problem with the server hardware/resources or the windows 2000 server OS install, but I fail to see that as the reason when all is well under the 8.5 engine and broken with the 9.1 engine (and the most current available 9.5 version) even on the original server now functioning as a test environment. Help!!!!!
 
Do any of the other visual tools such as visual menu builder, visual scheduler, etc. still work?

What error messages are you seeing in your ODBC trace?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
What interface are you using? PWE or Progression Explorer? Do you get the same error in each?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
I'm using Progression Explorer, but I don't know anything about PWE. Visual Menu builder works and I'm sure Visual Scheduler, as well. I believe only Visual Bill Builder is not functional. I get the 3704 error and then it does pull up the screen, but it is totally disfunctional, only a shell. I have to go into the office tomorrow so I'll post the ODBC trace for you then. Thanks for your help.
 
Try this using PWE and let us know the result.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Here's what fixed the issue:
*Clean install of 7.6.300 in Demo mode
*Applied Psql9c.exe
*Applied HT12262558
*Tested Visual Bill Builder which worked
*Copied in registration file
*Copied over DATA directories
*Visual bill builder worked
*Copied in the previous Screens directory because we have numerous custom screens we needed to move over
*This broke Visual Bill Builder again
*Applied the DDFupdater
*Still broken Visual Bill Builder
*Restored the previous Screens directory and copied in each screens file testing Visual Bill Builder after each
*Tested Visual Bill Builder which still worked
Not sure what was causing the error, but I now have a working 7.6 300c with 9.1 engine. Long way around, but at least it now works.
I really appreciate all the help. Thank you all.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top