Topics Search

Access Error 2950!

Access Error 2950!
Views: 44
I have an access .accb file with one form.
On the sub:
Public Sub Form_Load()
End Sub

When the form loads, it sets focus to combobox1. EASY RIGHT?!?!?!?!?!?

It works perfectly fine using Access 2007 on Windows XP.

When I open it on Access 2010 on Windows 7, I get Run-Time Error '2950'! Tried 4 different computers all with the same error!
Sponsored Links:

More topics


Error 2950

I downloaded the Access template for school student database last summer. I had no knowledge of access, but did some research and re-worked this template to make it work for my school. About 5 months ago we started getting problems and errors. One of the most recent is error 2950. What does this mean

Error 2950 with TransferSpreadsheet

So all of my users can run my macro to import data from excel into the access database, however sometimes they will ranomly get the following error

Action Failed
Macro Name: Import
Condition: True
Action Name: TransferSpreadsheet
Arguments: Import, 10,Offline, O:\Access\ImportOff,Yes,
Error Number: 2950

Im not exactly sure why this error is appearing, the MS documentation I read stated that this error occurs when the database is not in a trusted location but I have checked and confirmed that it is, does anybody know anyway to resolve this

2950 Error in Access 2007

I am running Access 2007 (SP1) on WinXP

I have created a macro that calls a function from within it. However, whenever you run the macro the 2950 error comes up. I have set my database folder as a trusted location but it still happens.

Assuming this is a bug, can anyone suggest another way to run the code. Incidentally, when I try to run it direct from the Switchboard I get an error returned as well (although it doesn't tell me why). The functions does run fine on its own when done manually.

Access 2950 error

I am getting a 2950 error. I looked it up on MS support but the solution did not work. So let me explain. I have an Access program that is a Macro calling a VBA program via scheduler on a server. The program is run with AC2007 runtime.
It loads data to a back end database. The program is getting this message.
Action failed
Macro Name: ImportCounts
Condition: True
Action Name: RunCode
Arguments: LoadCounts()
Error Number: 2950
I have checked the Trusted locations and added the program location in the program. I was told this is a local setting and can not be set on the server because we are using AC2007 runtime. Anyway changing the settings did not effect the message. Is that true? How do I get the program to run

Errors: 2950 AND 2109

I have created a macro to go to a control on a form on click of a button. The control is definitely on the form, visible and enabled and referring to a field within the table but I sometimes get an error.

The error number comes up 2950 which generates a run time error 2109 stating no field named in current record.

As the field is in the table that the form is bound to I have no idea what the problem is and it only comes up with the error occasionally. How can I prevent the error from ever coming up?

Marco error 2950

When I click print on a form to run a reports, if report uses a TABLE as the input source it work fine. If click print and the report uses a QUARRY as the input source, I get a macro error box with error code 2950. Why & how can I eliminate this problem

Error 2950 In Access 2007 Runtime From Trusted Location

I am deploying an Access 2003 database in a network environment using the 2007 Runtime to run the DB. The front end runs off of the local computer and the backend off of a network location.

I have both databases in trusted locations that I have added through the registry. I have enabled network locations. I do not get a prompt indicating that they are not trusted, which shows me that they really are in trusted locations.

I have the full version of 2007 on my laptop and get no errors, however, on the client machine I get a 2950 error in the Autoexec macro.

I tried moving the function call in the macro into a form that would launch on startup instead of the macro and still get the runtime error, however, when I get the error in this fashion I do not get the error dialog like with the macro, I just get a runtime msgbox.

Error 2950: using combo box on form

I have a combo box on my form that I use to search my records. We use it to select a client and have that client show up on the form. For some reason, the original combo box we had stopped working, so I tried to put another on using the wizard and deleted the original that had stopped working.

Now when I try to use the combo box I get an error. The drop down shows my clients and it allows me to start typing their name and have it show up, but when I select a name I get the error"procedure declaration does not match description of event or procedure having the same name" When I select "OK" on that message box an "action failed" box pops up with the following.

Error Number: 2950

I did a search for error 2950 and nothing that helped came up. I have enabled macros and selected to trust the source.

Error 2950 In A2007 in AutoExec Macro From Trusted Location

I'm running Access 2007 on a Win XP box. I have a make table query to create a local table from linked Oracle tables. I have been running this successfully for a couple months in a trusted location from an AutoExec macro via a scheduled overnight job.

I recently started receiving a 2950 error when running the query from the macro, but when I run it manually itcompletes successfully.

Problem With SetValue, but Only On Certain Forms

Basically, my database is for HR and uses a series of forms to enter a new hire, and to export this new hire to excel for a data upload. The weird thing is that it worked before, then all of a sudden, it gave me error 2950 while trying to run a macro which had a few SetValue functions.

I went to another form to see if that one worked w/ SetValue (because the database is trusted in my system), and it did. So my problem is that I'm receiving error 2950 (trust issues) inone form, but not receiving the same error, from the same function, on another form.