Run time error "438" - Not sure which category it needs to be in.

[Cookie9123]

Hello,
We have a customer that runs a SQL DB through an Access front end (I think that's how it works). On one of the PC's, it has started to come up with a run time error when trying to get into one area fo the DB through the menu. This is only happening on 1 PC and it is fine on the other 6. I have checked and the coding looks to be the same on all PC's including the 1 that is showing the error. I have relinked the ODBC connections and these show successful. Below is the error that shows and when I click debug it takes me to the line shown highlighted, but like I say, this shows as the same on all PC's. They are all running the same OS and SP and look to have the same updates installed.

Hoping someone might shed some light on what is happening or offer advise in what I can do to check/fix the issue.
Thanks in advance.
Lee

 

[theDBguy]

Hi. What is dtpDate?

 

[CJ_London]

what is dtpDate? The error message is indicating it is an object of some sort and it does not have a property called FirstDay

 

[Cookie9123]

Thanks for helping. The DB was setup by another company and I have little experiance with Access and SQL databases. To give a little contect, the DB is do do with a fruit for schools database, where the terms etc and what fruits are being sent are imputted at the start of the year. This particualer error happens when the user clicks on the menu item called orders. The dtpDate.FirstDay I believe points to the first day that the order is implemented. I can try and find out more, but not sure how. I can tell you that this is exactly the same as what it says within the data on the other PC's, so not sure why this one does not work. If someone can help me in getting further information, then I can try and get it.

Thank you.

 

[Deleted member 147267]

I would go to the problem pc(s) and see if there are any missing or broken references. I say that with the assumption that the error would be the same in the that case, although one would logically expect Access to complain about the fact that the object isn't recognized if it's missing, not that it doesn't have a particular property or method.

It could also be that 1 user is doing something that the developer never thought of and neither has anyone else thus there is something wrong with the instantiation of the object. This user does not see the Access security warning at the top of the application screen by any chance?

 

[MajP]

I put my money that dtp is an active X Date Time Picker since that is the normal prefix. The property is .FirstDayOfWeek which appears to be what was intended. However, I am not familiar with the NW prefix on monday. I am guessing this is a third party active x control

 

[The_Doc_Man]

If that Date/Time Picker is a correct guess and the FE is replicated to each user then something else must be going on, because that code would fail everywhere unless this is the first time anyone ever tried it - and that seems unlikely since the event is Form_Current that EVERYONE would try. So I'm kind of guessing that MajP is correct about it being some 3rd party object.

 

[CJ_London]

Good spot - if it is an activeX control, then it is possible the problem machine is running 64bit access/office rather than 32bit - activeX controls are bit specific

 

[The_Doc_Man]

Good point, CJ.

Cookie9123: On a machine that is working and a machine that ISN'T working correctly for this error, there is a simple test to be run.

Open Access on each machine. Doesn't even have to be an app launch. Just Access itself.

In the ribbon to the left is FILE. Under FILE, find HELP. Click that. You'll get a couple of different things on the screen. On the right side, there will (probably) be a Microsoft Office logo of some flavor. Under that will be the version number and bitness of that version of Access. You want to compare the bitness (32 or 64 bits) on the two machines. If they are the same, then this experiment wasn't that expensive even though it says nothing. But if they are different, that very well could be the problem. Access doesn't work well in mixed "bitness" situations.

BTW: Your original implied question of which topic? General was indeed appropriate. Good guess.

 

[Cookie9123]

Thanks all for the responses, its is very much apprieciated.
@Micron. There are no security warnings and they have been happily using the application for awhile. Everyone does the same thing, clicks in the menu for orders and it takes them to an orders page.

@MajP adnd @The_Doc_Man. You could be right in that it is a 3rd party Active X control, this does ring a bell.
@CJ_London and @The_Doc_Man. I will check if they are running 32 or 64bit.

Thanks everyone. Once I have taken a look later today or tomorrow now, I will update.