0

I'm trying to make an app using Microsoft Visual Basic 6.0.

My problem is that VB cannot open tables, outputing a message "Could not open table 'Table'!" though Visual Data Manager opens it fine.

What could be the problem? Could it be something with CRYSTL32.OCX and DBGRID32.OCX file that also cannot load? Or there's something that should be corrected while an app in AppModeler is generated?

P.S. Tables generated in MS Access using *.vbp script file are filling in OK.

HardRock4Life
  • 177
  • 1
  • 9
  • 1
    If it's VB6, it should not be tagged vb.net – Phil M May 04 '17 at 17:00
  • Yes, it's VB6. Where can I untag it? – HardRock4Life May 04 '17 at 17:04
  • 1
    Edit the question by clicking the `Edit` link underneath the question text. At the bottom of the edit window is a section headed **Tags**. There you can click on the "X" next to `vb.net` to remove that tag and you can also type "vb6" to add that tag. – Blackwood May 04 '17 at 17:59
  • If you have two OCXs that can't load, would probably be worth fixing those, and see if that does indeed fix the other issue. Might be a dll common to the 3 is missing or such – Phil M May 04 '17 at 22:31
  • So, today I tried to load my project on another computer, which has Windows XP as a root OS (my XP is on Virtual Machine). The result is - absolutely everything loaded fine, no errors at all. Except for the tables while running Visual Basic app - it still says "Couldn't open table!". So the reason is not those *.OCX files, but smth different. So far, no more ideas, what could be the problem. – HardRock4Life May 05 '17 at 10:23
  • If your references (such as the 2 OCX files mentioned) are properly registered, the OS version likely has nothing to do with it. – StayOnTarget May 05 '17 at 11:20

0 Answers0