Errors Solutions
error

For the Programmers. What is the solution of VB error 3051?

Q: I applied an MS Access to a CD but when i run the program, runtime error 3051 occured, "The Microsoft Jet Database apparatus cannot open the file 'E:\catalogfiles\catalog.mdb'. It is already open exclusively by another user, or you need allowance to view its data". Can anybody help me solve this problem?


A: You can't offer an access file from a CD. It needs to be on a writable drive (eg flash drive or hard enterprise). Also, you possibly burned the .ldb file onto the CD, which you shouldn't, because it indicates that the database is locked.

5.3(3) Calculator in Visual Basic Part 3 - Perfecting Code

Putting the finishing touches on the encipher by dealing with the zero division "error" (in versions prior to VB 2005, this would be a runtime error ...

Reacting to the Mousewheel

The record of mouse wheel support is pretty ragged. Originally, Windows 95 stomach was non-existent -- only Intellipoint provided a registered message to work with it. Windows 98 and Windows NT 4.0 added some natal support, in the form of WM_MOUSEWHEEL messages. Much later, a new message was added for horizontal scrolling. Since so few controls knew about these messages initially, Microsoft adopted the blueprint of sending the same message to a window's parent if the window that initially got the message failed to moved to it. Therein lays our opportunity.

We can hook the message stream for a form, and sink mouse wheel messages for all the controls that don't prepare these messages themselves. I haven't spent any serious time looking at these messages in close to a decade, and was in reality caught by surprise that many of the intrinsic VB controls have acquired mouse wheel smarts as the years have gone by. This can only be because the underlying starting-point class was updated, but it's fun to see that in XP almost all of them work just fine. Others, like the native scrollbar controls, still sine qua non a power boost.

© 2008 Errors Solutions