Access issue's regarding forms.

rich2600

Total access newb.
Local time
Today, 07:17
Joined
Mar 12, 2007
Messages
10
Hello,

I found this creative and programmer based forum, and i'm very interested in being involved and helping and also getting help, unfortunately, as my first post i must ask for help. I have an access database, that's displaying an OpenForm error in some locations of the network, and some not. If you wouldn't mind, tell me if it's code related or something external, as i am not advanced enough to decipher that myself. Thanks.

Code:
Private Sub Command61_Click()

On Error GoTo Err_Command61_Click

 

    Dim stDocName As String

    Dim stLinkCriteria As String

 

    stDocName = "frm Calendar"

    DoCmd.OpenForm stDocName, , , stLinkCriteria

 

Exit_Command61_Click:

    Exit Sub

 

Err_Command61_Click:

    MsgBox Err.Description

    Resume Exit_Command61_Click

    

End Sub

-Rich
 
At a guess, the form contains an ActiveX object that's not installed on some PC's.
 
Thanks alot. I tried it on my local machine where i refuse most activeX scripts, and it didn't work.. So that explains alot. I will update the other locations on the network. Thank you!
 
yeah, but i really can't reprogram the database, it's just more so my job to fix it, and i put up the ado and it's still malfunctioning, is there a specific ado i should be looking for?
 
Not sure what you mean by "put up the ado". If indeed the problem is an ActiveX control, the normal solution is to make sure that control is installed on each of the PC's.
 
yeah, but i really can't reprogram the database, it's just more so my job to fix it, and i put up the ado and it's still malfunctioning, is there a specific ado i should be looking for?

Well, sometimes to fix it, it must be reprogrammed. For example, I had an issue with a field in a form that everyone was accessing and changing. This caused a lot of confusion for others - so, I had to go back in and lock that field.

I don't use activeX controls for the same reasons that Pbaldy mentioned. That includes any calendar that appears on my forms. That way, you know it will work on 99.9 of all machines. Just my thoughts.
 
Not sure what you mean by "put up the ado". If indeed the problem is an ActiveX control, the normal solution is to make sure that control is installed on each of the PC's.

ado (ActiveX Data Objects). The problem is i can't find the proper activex controller. Thanks for being so consistent. I really appreciate it.


Well, sometimes to fix it, it must be reprogrammed. For example, I had an issue with a field in a form that everyone was accessing and changing. This caused a lot of confusion for others - so, I had to go back in and lock that field.

I don't use activeX controls for the same reasons that Pbaldy mentioned. That includes any calendar that appears on my forms. That way, you know it will work on 99.9 of all machines. Just my thoughts.

Thanks again for the awesome suggestion and i will keep it in mind for future projects. Unfortunately, i only have 2 months with this company, and as the residential web design/program design, i have alot of projects, this one being the lowest, so i can't put a massive amount of times toward it. Therefore only allowing me to fix this situation.
 
I for one don't EVER use spaces in my Object Names IE "frm Calendar"

Mick
 
ado (ActiveX Data Objects). The problem is i can't find the proper activex controller. Thanks for being so consistent. I really appreciate it.

ActiveX Data Objects is not an ActiveX Control. It is an Object Model which allows you to connect to data sources and use recordset objects to be able to read, add, and edit data.

An ActiveX Control is a control that is an object that is able to be used (calendar, rich textbox control, etc.) which is compiled into an OCX file and with which, if not registered on a user's machine, is not available. It is sometimes possible, depending on the licensing for the particular ActiveX Control, to copy the OCX file from one machine to another and then register it using a command line of
regsvr32 <path & filename of dll or ocx>
to register it. However, not all ActiveX controls are available this way.

So, just like some of the others here, I choose to not use them, if at all possible, due to the problems of users not having them all of the time. When I do absolutely need to do so, I create a Visual Basic 6 project with just a bogus form with the control on it and create an install program to install it so that it becomes available. (but I have access to VB6 at work as well).
 
ActiveX Data Objects is not an ActiveX Control. It is an Object Model which allows you to connect to data sources and use recordset objects to be able to read, add, and edit data.

An ActiveX Control is a control that is an object that is able to be used (calendar, rich textbox control, etc.) which is compiled into an OCX file and with which, if not registered on a user's machine, is not available. It is sometimes possible, depending on the licensing for the particular ActiveX Control, to copy the OCX file from one machine to another and then register it using a command line of
regsvr32 <path & filename of dll or ocx>
to register it. However, not all ActiveX controls are available this way.

So, just like some of the others here, I choose to not use them, if at all possible, due to the problems of users not having them all of the time. When I do absolutely need to do so, I create a Visual Basic 6 project with just a bogus form with the control on it and create an install program to install it so that it becomes available. (but I have access to VB6 at work as well).

Thank you very much for clarifying that for me. I'd hate to be persistent, but what ocx file would handle forms in access?
 
Again, I think we need to clarify. Forms are not ActiveX controls, nor are they ActiveX Data Objects. Forms are internal classes within Access and they are not accessible, except through the interfaces provided.

You likely have a CALENDAR ActiveX control on your form, which the CALENDAR control is probably causing your problem. Double check and then if it is on there, I would go with an ActiveX-less modification where you would delete that control and use something like this:
http://allenbrowne.com/ser-51.html
 
Again, I think we need to clarify. Forms are not ActiveX controls, nor are they ActiveX Data Objects. Forms are internal classes within Access and they are not accessible, except through the interfaces provided.

You likely have a CALENDAR ActiveX control on your form, which the CALENDAR control is probably causing your problem. Double check and then if it is on there, I would go with an ActiveX-less modification where you would delete that control and use something like this:
http://allenbrowne.com/ser-51.html

Thanks for the simplistic step through!! I guess i was looking for the simple-ist answer available, hoping that it wasn't to edit the database, but ultimately that looks like what i'm going to have to do. so thanks to pbaldy, boblarson, wiz47 and dreamweaver, i'll open a topic soon displaying my newbish-ness. :)
 

Users who are viewing this thread

Back
Top Bottom