Before I start on this seemingly endless journey of learning Access 2003, I thought it appropriate to ask the question;
Will this program do what I need it to do?
I apologise in advance if this is not the right place to ask the question, I am a complete beginner to Access 2003.
I want to make an electronic log book for the guys at work, there are 5 people of different trades who would need to keep the log.
A typical entry would be as follows
Mon 22/3/06 Alan Smith B Shift
Compressor house (heading)
No 1 compressor (plant)
Oil pump (component)
Filter cleaned (action taken)
Personel (heading)
John Jones (personel)
Phoned in sick at 15:00hrs, will phone tomorrow to update
Boiler house (heading)
No 4 boiler (plant)
Water vlave leak (problem)
Tightened gland (action taken)
There are many headings, probably hundreds of plant, thousands of components and actions taken
We would need to view events to particular plant or areas between certain dates, some personel would need to enter data, some would only view the data without being able to enter it, few would need to alter the data.
Is Access 2003 capable of this, should I start the journey?
I am looking for a program that will repair a MsAccess 2000 .mdb file. So far all I have been able to find is those that repair the tables, does anyone know of a program that will repair the entire file including the forms?
I believed that Access is a stable DB program. It looks like I may have to change this view. Yesterday, due to some fault in power supply (SMPS), my PC suddenly went off while I was working in my Access DB. My DB is a personal DB (single user). Today, after replacing the SMPS, when I opened my DB, Access gave a message that my DB is corrupted while it was being used last time. It asked to attempt repair with Yes/No button. I clicked the Yes button and it did nothing. In my third attempt, I was able to open my DB but I am worried whether it will work as before. Could the experts in this forum throw some light about Access DB' stability and measures to prevent corruption? Grateful for advice.
Can anyone tell me how on a macro to call another application. I am trying to open up a mainframe session so need to run something like c:mainframe.rsf???
Can anyone suggest a good program that will handle scheduled emails to people in our Access database? I need to send an email automatically to each of our employees on their birthday. I need the program for much more than that but that is what I am working on at this time.
I have noticed diagrams showing Microsoft SQL Server accepting SQL statements sent by “SQL Requesters” over connections. I would like to know if Microsoft Access can be used in that fashion?
Put another way, can Access be configured to accept an SQL statement that another program (e.g. a VBA program in a VBA enabled 3rd party app) creates?
Currently, my VBA program instantiates an Access database object and then manipulates it (I just add a record to one of the tables), then closes and destroys it. This solution seems fragile (it stops working—I can explain more if needed). I would like to know if the technique inferred by my question would be more reliable.
We are having a problem with mulitple users leaving an Access db open and then I am not able to make new reports, etc. without calling everyone to close their session.
Is there a way to automatically close a db if user has not used in certain amount of time?
I have a VBA program that I wrote in access. My question is this: Is there anyway to eliminate or minimize the main Microsoft Access program window so all the user would see is my forms and the desktop? Not that ugly gray back drop? Thank you in advance for your help.
As in the topic stands that im looking for a code that hides Access and it starts up like a normal program. Ive searched several things on the forums and i actually did found something only he didnt gave the code ;(.
I am new to this forum as I recently started working in MS Access. I’m hoping someone can please help me with this query I’m trying to do using MS Access 2007.
This task is somewhat similar to a typical points/miles rewards credit card program.
The problem is as follow:
For every $2,000 of accrued purchases in a credit card, an individual will get a gift card.
So, any remaining balances over $2,000 will rollover and be added to next set of transactions, until it reaches $2,000 again. For instance, if on the first week I spent $2,500, I would qualify for my first gift card. The excess $500 would rollover and be added to the next set of transactions until they reach $2,000 again. Therefore, this would qualify me for another gift card.
So far, I’ve created two tables, one that stores accrued purchases (Promo History) and another table based on an Append Query which takes all qualified transactions from the first table and appends those records to the second table (Promo History Qualified) in order to track those qualified transactions over $2,000.
However, I’m stuck on how I would accommodate the remaining balances to be carried over. Any suggestions would be greatly appreciated!!
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 am trying to prepare a mini budget program in ms access for my personal use in my office , but every time i fail to do so, my tables are as under
Field Name Properties Code ID AutoNumber 001 Cash 002 Bank 846 conveyence dt: Date/time Code text (list selected by drop-down list) des Description Bill currency yearly Budget currency quartlyBudget currency
Query Question:
Group Aggregate function in my Budget data base file
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 have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2 Office: Office 2003 SP1 Jet: 4.0
