combo box broken ?

[GaryPanic]

Guys -

i have a couple of combo box's on a form and they are find record combo drawing from a list (one is a number the other is a name)
anyway they have both stopped working - ?


Runtime error "48"
errori in loading dll


- well i thought just re do them -

nope its not letting me - what I have cocked up ?

regards
(and help please)

g

 

[GaryPanic]

nope didn't work...

 

[GaryPanic]

its a DAO problem (I think)....



I am running 2000 d/b on Access 2003


I tried updating a copy to 2003 - nope still buggered

 

[GaryPanic]

Read this and I was hoping not to have to do this -

I will first baack up date uninstall everything - then reinstall and see if that helps....
what a pain ...

 

[GaryPanic]

i am going to try this --
http://msdn.microsoft.com/en-us/library/aa159923(office.11).aspx

 

[GaryPanic]

Still no...
OK actions so far -

full back up
uninstall office
register cleaner (Glary)
reboot
reinstall office no change

apply updates
no change - any idea's

 

[SOS]

Does it work on other computers or does it fail on all? If it fails on yours but not someone else's then that would imply a different troubleshooting path than if it doesn't work on all of the computers (which would likely be a database file issue at that).

Is this a split database? Does the combo's recordset refer to a linked table which isn't linked anymore? (just grasping at straw here)...

 

[GaryPanic]

Does it work on other computers or does it fail on all? If it fails on yours but not someone else's then that would imply a different troubleshooting path than if it doesn't work on all of the computers (which would likely be a database file issue at that).

Is this a split database? Does the combo's recordset refer to a linked table which isn't linked anymore? (just grasping at straw here)...

Its not split at the moment
and on my old laptop (pre historic ) its seems to work
the full fault is
MS visual basic
runtime error 48

error in load dll

i have tried a just adding a combo box - and it isn't happy - just won't let me...

 

[SOS]

Is your service pack level exactly the same on your two machines? It does sound like that might be an issue. Either that or a subsequent hotfix that was applied on one but not on the other. This stuff can be a pain trying to diagnose.

Also, have you tried importing everything into a brand new database file?

 

[GaryPanic]

"Also, have you tried importing everything into a brand new database file?"

Yeah - step one after compact repair
then lots of swearing ...
I am into google territory now

 

[GaryPanic]

Thought I would put the code up - but it seems ok to me


Private Sub Combo52_AfterUpdate()
' Find the record that matches the control.
Dim rs As Object

> Set rs = Me.Recordset.Clone
rs.FindFirst "[Quoteid0] = " & Str(Nz(Me![Combo52], 0))
If Not rs.EOF Then Me.Bookmark = rs.Bookmark
Me.Postcode.SetFocus
Me.CSIexpeneses.SetFocus
Me.Combo99.SetFocus

 

[SOS]

See if changing this:

Dim rs As Object

to this:

Dim rs As DAO.Recordset

makes any difference (not sure it will but trying everything I can think of to help)

 

[GaryPanic]

Nope ..... no change


what libarieres should I have referenced ...


Error in loading DLL (Error 48)
The specified dynamic-link library (DLL) can't be loaded. This is usually because the file specified with the Lib clause in the Declare statement is not a valid DLL.






Possible causes for this error are:


The file is not DLL-executable.
The file is not a Microsoft Windows DLL.
The file is an old Microsoft Windows DLL that is incompatible with Microsoft Windows protect mode.
The DLL references another DLL that is not present.
The DLL or one of the referenced DLLs is not in a directory specified by your path.

 

[SOS]

What do you have in your references? Can you provide a screenshot?

 

[GaryPanic]

here you go - this is a real bummer

 

[SOS]

You have Word 2007, but the rest of Office is 2003?

 

[GaryPanic]

no it should all be 2003

 

[SOS]

Uncheck the Word 12 reference, which is Word 2007. That should help.

 

[GaryPanic]

No change



I found this ..my DAO was missing however reinstalled it - and the problem contines



lifted "
I used a batch file registering some DLL and OCX for another
application here at job, and we found out that it solved our MSaccess
problem at the same time. So I ran a few test in order to find out
which DLL was the one responsible for the problem and evidence pointed
out DAO360.dll, on the other hand, I didn't have the time to check if
the rest of the database was still entierely usable with only
DAO360.dll and not the rest of the DLLs from the batch file, so my
final words on this are:

If you encounter problem with various MSACCESS wizards and VBA code,
DAO360.dll might be the buggy DLL that you need to register correctly.

For other problems, it might be useful to try to register any of these
files (they were in the batch file I talked about):

MSSTDFMT.DLL
Comdlg32.ocx
Scrrun.DLL
msrd2x35.dll
msjter35.dll
msflxgrd.ocx
RICHTX32.OCX

 

[GaryPanic]

just tried to import into new dbase since my last action what does this mean ?

The Visual Basic for Applications object library is no longer a standalone file; it is integrated into the dynamic-link library (DLL).

In earlier versions, when you started an application that uses Visual Basic for Applications, certain object libraries were loaded. This error has the following cause and solution:

An attempt was made to load a previous version of the Visual Basic for Applications object library (vaxxx.olb) or host-application object libraries. However, the correct language version of these object libraries could not be found in the system registry.
Reregister your application. On the Macintosh, delete the vba.ini file from the Macintosh Preferences folder, and restart your application.

For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).