Program Working In Access 2007 Not Working In Access 2010 Due To Missing OCX File
Dec 27, 2014
I have a program that runs under access 2007 that I use at my work. We will soon be updating to MS office 2010 and the program will not work now because a calender file .ocx was removed from access 2010. Is there a way to get the 2007 .ocx file to work in access 2010?The program I am using is a relatively simple stand-alone and unsupported app that we use to request patient arrival and departure from various radiology tests inside a hospital. No reports are made from the app other than the number of patient transports for the day.
The app is placed on a common drive accessed from any pc in the hospital. No special permissions are required. But our app does use the calendar, time and date functions in access 2007. When I tried the app on a pc with access 2010, it basically says it (access) cannot open the app because a .ocx file is not present.Is there a way to make the access 2010 calendar file work in access 2007?
I am Using Access 2010 Version. I have created a Database which consists of Linked Tables (from remote Server), Queries and a Form.
I am using Form to search the required Data. Every thing is working in My PC. But, when the Database file is trying to open from my colleague PC. It is not working. I mean, The Form is opening but when I click the Button nothing is happening. My Colleague is using 2007 Version of MS Access.
date formula that I was using in access 2007 doesn't seem to be working in 2010.
The formula that I had was
Between DateSerial(Year(Date())-IIf(Month(Date())<4,1,0),4,1) And DateSerial(Year(Date())+IIf(Month(Date())>3,1,0),3 ,31).
The calculation allowed me to count holiday hours taken between 1st April and 31st March. The problem is that it was working up till 31st march but is not now showing holidays taken since 1st April.
I have built an Access 2010 split database on my computer and it functions as built. My next step was to copy it to the server at work and test it. I discovered the tables had to be re-linked and so did that. As I have read in the Access World Forums in order to function as a multi-user database a copy of the front end must be placed on the individual workstation with the back end residing on the server, however the hyperlinks in the back end will not function when the copy on the workstation is run. I simply get an unable to open "filename" error pop-up. I can run the server copy and everything functions as built. I know that the hyperlinks require all the files to be in the same folder (relative vs. absolute), but if the back end contains all the hyperlinks why does the location of the front end seem to affect the operation of the back end?
I have a fully operational Visual Basic program that uses MS Office XP and it's related MS Access. Because of security concerns, I recently upgraded to MS Office 2007 and MS Access 2007. I can open MS Access 2007 using the shortcut on the desktop and run any of the database queries. When I try to run the Visual Basic program (called prjPathfinder) and open Access 2007, it says "Error 5: The type initializer for prjPathfinder.Upgrade Support threw an exception". It then shows the first form in prjPathfinder but does not open Access 2007. What am I missing?
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I've been updating the look of some of my db's and am trying to access the new style colour picker per Office 2007/10.
Up to now I have been using
Private Declare Function ChooseColorAPI Lib "comdlg32.dll" Alias "ChooseColorA" (pCHOOSECOLOR As ChooseColor) As Long
which displays the pre 2007 style.
I've looked all over the web but cannot find anything relating to the current style (other than using it from the ribbon or control properties), so not sure if I should be looking for a different function or a change to the ChooseColor type values.
All db's are running 32bit access and at the moment 32bit OS but will no doubt have OS upgrades to 64bit soon.
I've just started using 2010 and, unlike previous versions, the expressions that I've put on controls in a form are not working. Is there a setting that has to change that's new to 2010?
I am using an update query comparing 2 tables to add new records from table 2 to table 1. This worked fine until we upgraded to Office 2007. Is this a function of 2007?
I am not getting any prompts to OK, "You are about to update 1500 records"
I am having a hell of a time trying to make my order and invoice processing database to work properly with useful functions. Is there any online resource from which I can download a working example of such a database in order to use as a case study and examine how everything relates and how complex order forms are created? :confused:
My access installation opens databases reasonably well. I can create databases, add tables, etc. However, I cannot:
1) Add a command button or data-related fields to a form: the "command button wizard" stops responding on the first screen. If I click "Cancel", the button depresses, but the wizard doesn't close. 2) open the "Linked table manager": Access crashes 3) import an Excel spreadsheet: Access crashes
I suspect these might be related.
I've tried these with various databases, some on my local C drive. I have also tried these with various excel files. Not being able to add data items to forms is particularly irritating -- I don't want to build my own front end (that would sort of ruin the purpose of using Access, except that it happens to be a database already on my desktop).
One other thing -- when I start up a database, it always gives me an initial "Installing components" message. This occurs similarly for other MS office applications as well. I don't know whether this is related. I do have admin rights on my local machine, and have tried the "Repair MS Office" function in the Control Panel.
I don't necessarily expect an "answer", though some advice on how to proceed would be great.
I'm beginning to think it is a windows issue and not access issue. I have a couple of users that weren't able to click on the form shortcuts on thier desktop. They had been able to use them earlier in the day, but later double clicking them would not bring up Access. I had them use Window's explorer and try to click on the MDB file to bring up access, but that also didn't work. But launching Access directly, then open existing files, would open up the database for them.
Rebooting let them use the shortcuts.
Any idea what might cause this? They have been using the application for a couple of months without mishap until today.
Has anyone seen this behaviour before. If so, how did you fix it?
My company recently upgraded our MS Office from 2007 to 2010 (except for Access).
Previously, when I had Access 2007 and Outlook 2007, I had a process that generated 50+ dynamic emails from an Outlook template file (.oft).
The code would loop through a listbox and replace the template's default text to a string of text specific to the selection in the listbox by utilizing the Replace() function on the MailItem .HTMLBody.
Since the upgrade to Outlook 2010, the code is able to run, however, the Replace() function is no longer working; Instead, each email that is generated maintains the template's default text.
The only thing that is not working is the Replace() function, all other aspects of the code work fine.
I've provided a simplified version of the code below:
Dim myOlApp As Outlook.Application Dim objMailMessage As MailItem Dim stBody As String Set myOlApp = Outlook.Application Set objMailMessage = myOlApp.CreateItemFromTemplate("C:UsersDesktop emplate.oft")
[Code] .....
I've recreated the template file in Outlook 2010, thinking that the template created with Outlook 2007 would be the culprit, but to no avail.
What could have changed from Outlook 2007 to Outlook 2010 that would render my previously valid code ineffective?
Are there certain references I need to enable in both Access and Outlook to allow VBA in Access modify the content in an Outlook email?
I have a SQL Enterprise server that I am using a MS Access to remotely access and populate the tables from my laptop into a database.
Based off of the linked data between my project and the true SQL database, I have created some Access Data pages for interacting with the data.
What I need to know how to do is how do I modify the Access Data Pages (source code), so that instead of using my local access project file for source of data it points directly at the SQL database and can operate on the web only interacting with the SQL not my computer anymore.
---Greater detail if I didn't do a good job with the description above---
SQL Server A has database 'Helpdesk'.
IIS Server B for webpages (.aspx).
Computer B has a .ADP (Access Data Project) called 'helpdesk.adp' which is linked via SQL username and password to Server A's 'Helpdesk' database.
Computer B has several Data Access Pages that are used to manipulate the database data.
Problem1: Convert Data Access Pages to normal web pages (.aspx) on Server B so that they talk directly to Server A's 'Helpdesk' database via SQL username and password and no longer care about any reference to Computer B?
Problem2: What functionality from Data Access Pages can not be carried over to a (.aspx)?
I tried posting this before, but I have not seen it posted yet, so I will post again.
I am trying to import an excel sheet into access. I have searched the threads, and found similar problems, but none of the answers are helping.
The problem: I use a macro to transfer the spreadsheet (Transferspeadsheet)
I have a column in excel that contains mostly numeric entries, but sometimes it will have alphanumeric entries.
Access will see the numeric entries and assume this is a numeric field- and then null my alphanumeric entries, and I will get importerror tables after the fact.
Many times the first 10 rows are completely numeric, but the 20th row is alpha numeric. If the alphanumeric row is closer to the top- no errors.
I have 60 spreadsheets to load every morning. Switching to access for all users would be a godsend, but also a fantasy in my environment. I have to find a work around for this. The users will always be using excel to enter this data.
I have tried:
1) Changing excel columns format to text.
Result: Access doesn't care. Sees the field as numeric- import errors on alphanumeric entries
2.) Linking to table
Result: if the first rows are numeric, when I scroll down to the alphanumeric entry it states "error" when I view the linked table in Access. (Access will not allow me to change the field properties of the linked table)
3.) Making a table in access with the "correct" feilds and exporting to excel. Having the users use that version.
Same result- import errors.
There is one thing I have not tried, and I am ready to try anything: Somehow exporting excel to text and then importing the text.
HOWEVER: I read this as a solution someone has tried in this forum- but he had problems with date entries. (They didn't convert very well, I am assuming).
I have date entries in my spreadsheets, so I don't want to go there. Besides, I don't know how to automate the export of 60 spreadsheets to text.
I asked someone else, he suggested an "import map".
Did help search, Internet word search- nada.
Is there some sort of import template that can be used to force access to understand that I want a particular field as a text field?
I have a 22 column report where I am trying to builld search criteria so you can search everything and anything. I have everything from texts, (comments tools) to numbers (weekly periods and reference numbers). Its hard to explain clearly but have tried to get this working. Basically, so far, I have built like and or statements for each column. The Query will run but will not be in any order. If I build the following:
A = Like "open" or "closed" - Information open or closed B = Like "1" or "2" or "3" or "4" - Quarterly Periods C = Like "1" or "2" or "3" or "4" or "5" (all the way up to 52) - Weeks in Year
It is more complex than this, but if I build these statements and run a query, Access will search for them but will not bring out the required information. I need Access for instance to pull only the information for say A=open, B=2 and C=3. I dont want to see the rest of the informaiton in that Query. Any ideas how to build this? Please help.
why this IF and Nz statement in my code below is not working. I know the me.txtrefNo value is "" (null) on a form field with property set to General Number. Therefore the Nz statement should return a "0" as I specified making the statement true as in 0 = 0 and then execute the actions below to generate a reference number however this it now happening as it's rendering the if statement as false and showing me the message " Whats going On?" which is after the else statement.
Code: If Nz(Me.txtrefNo, 0) = 0 Then Me.txtrefNo = DMax("[refNo]", "[R_P_Data_P]") + 1 tmpRefNo = Me.txtrefNo 'testing variable value MsgBox (tmpRefNo) Else MsgBox ("What's going on?") End If
PS. Does this have anything to do with the table field format that the me.txtrefNo value will be saved to?
I have searched the forum for this answer but no luck. :(
I'm trying to calculate the amount of WORKING time between two dates in an Access database. At the moment i am just subtracting one date from another but this gives me all of the time in between including weekends and evenings.
I need this time to be calculated in hours.
In Excel i know there is a NETWORKINGDAYS function which does something similar but with days rather than hours.
At least if i could get the working days i could then convert it into hours.
I am working on developing a database that develops requests to send to another department. There are a lot of forms, macros, reports and queries. A user inputs information into a form, and then selects a command button that is attached to a macro that builds the request. Midway through the build, another form comes up to complete missing information. I was going along just fine - at the testing stage for this part of the process - when the database stopped working like it should. Some of the issues I am seeing:
1) If you open a new query and try to close it without saving it, it just keeps asking you if you want to save over and over even though you select No.
2) If you open an existing query and make a change, it closes it and saves the changes without any prompting at all.
3) Macros and forms do not work right. I have a macro that deletes the records from one table. The form for that table now shows #Deleted in all the fields instead of blanks.
If you compact/repair the database is good for one run through but then it doesn't work correctly again. I have had this issue in the past but have no clue how I break my databases! I have a general knowledge of Access, I am not really a VBA coder if I can avoid it at all costs. There must be something in the relationship between all my tables, queries, forms, etc but I have no clue even where to start to troubleshoot. HELP!!
I have a database with a table and 2 forms.One form (frmList) is a list of all records in the database, and the other form (frmInput) displays fields for a single record.There is a button in frmList which runs the following script. The user clicks a record in frmList, clicks the button, and the selected record opens in frmInput. ID is a text field containing digits and an alpha that is in both frmList and frmInput.
Code: Private Sub Command9_Click() Dim ID As String strCriteria = "ID = '" & Me.ID.Value & "'" DoCmd.OpenForm "frmInput", acNormal Form_frmInput.Recordset.FindFirst strCriteria End Sub
This script works as expected in Access 2010. However we recently upgraded to Access 2013 and since then, this script causes Access to crash ("Access has stopped working..." dialog appears).I have stepped through the script and the line causing the crash is
I can't find any problems with syntax or anything about Recordset.Findfirst being deprecated in 2013 so I suspected some kind of file corruption. To resolve this I have tried: Compacting and repairing the databaseDecompiling and recompiling the VBA modulesCreating a fresh database and copying all the objects into it
could this be due to a missing library or something? Are there other methods of resolving a corrupt database if that is the problem? Or as a last resort is there an alternative method to Recordset.FindFirst that I can use to open a form to a particular record while retaining the ability to navigate through other records?
What I'm trying to do here is, update my access table ("Table1") from excel sheet ("Myexcel.xls"). Excel file contains all the information however access table is not updated except "RefNo" field. Condition what I coded here is when once connection is build, "RefNo" in excel matched with "RefNo" of access table , update the other fields in Access table. Which is working fine (doesn't showing any error) but still data is not updated in access table. I don't know why is not updating it....
Private Sub Command0_Click() Dim accessCMD As ADODB.Command Dim accessRS As ADODB.Recordset Dim accessParam As ADODB.Parameter Dim bFound As Boolean
