![]() Out of nearly 50 test systems (all of which have C++Builder 6), only a very small handful exhibit this behavior, and those are the only systems running Forms 8i, so there's a strong correlation and not much else. I'm not necessarily implying it's an Oracle problem, as it could well be a Borland problem, but regardless of fault, I'm hopeful that someone has heard of this before. ![]() I know this is a long shot, but thought I'd try asking anyway. The only way to "reset" the behavior is to reboot the system. However, once the Access Violation occurs, it will occur anytime a combo box is used, and it will occur in all applications, not just Borland ones. The combo boxes will work fine for a while (sometimes up to a day) before the Access Violation in VCL60.BPL occurs. Is there an equivalent package in Forms 8i? If so, what is it?įor reference, this has been observed on Windows NT and Windows 2000, and presumably occurs on other Windows operating systems as well. VCL60.BPL is a standard Borland designtime package for Windows applications (hence its relationship to the combo box). However, this seems to only happen on machines where Oracle Forms 8i and C++Builder 6 are installed, and it even occurs with combo boxes in non-Borland applications.īased on what I've seen, I'm thinking maybe using Forms 8i and C++Builder 6 together causes some sort of conflict in Windows common controls like the combo box.ĭoes anyone here use Forms 8i and C++Builder 6 together? If so, have you run into any similar compatibility issues? I have encountered a problem where combo boxes in applications will generate an Access Violation in VCL60.BPL (a Borland package).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |