Hi, I have hidden all the menus and added one of my own custom menus to a DB that I was creating. That DB has been completed. Now when I open a blank DB to commence again, I have the same hidden menues and my one custom menu. Is there away in Access 2003 that I can replace the template, for example, MS Excel and Word have .dot and personal.xls. Is there an easy way to bring them all back. I checked in startup for a restore defaults, however this does not work. Any ideas. Garry
I have developed an application and packed it into a runtime version. However, in the runtime version the shortcut menus do not work. The reason why I want the user to have that possibility is that the application has two hyperlink fields and it is much easier for the users to be able to browse to the documents instead of typing each link with all the errors that might give as well. Any help would be appreciated.
After searching through the "search" field, I realize lots of us are having problems with the menu's in access 2007.
After converting my 2003 DB to 2007, my menus are still there, but displayes as Add-ins instead of as the menu bar. I can't find any options to change during the conversion. I have tried importing my Logon window with the options "menus and icons" clicked, but this didn't change anything. If I open the DB in 2003 Format, then go to the options in Access 2007 I can choose the menubar, but if I convert to 2007, the menubar is only available as add-ins. Is there any way round this?
Appreciate any help - it is so time consuming trying to figure this out - and I seem to go round in circles, ticking options on and off... perhaps some dear soul has already found the answer!
I started access today and all my icons and menus are gone from the interface. I am forced to right click on all my queries and tables to perform any action. All I have at the top of my window is the usual "Microsoft Access" caption. Absolutely nothing else. Other than that, Access is fully functional provided I can use the right click commands. Has anyone encountered this? Help!
I have set up a secured database using access 2003 which I want to roll out to users who will only have access runtime installed on their pc's. The problem is there are some additional options that I want to add to a new menu (export, change password etc) that I need them to be able to view in runtime - when I set up a new menu in access 2003, it doesn't seem to be visible on anybody else's PC when they are logged into the database regardless of whether they have full access or runtime.
:eek: Our office is planning to switch over to MS Office 2007 including Access 2007. I've just been looking into converting our Access 2003 databases to the new version. One thing I noticed about the datasheets appearing as subforms is that each field header/label/caption/column selector thingie has a dropdown menu. The down arrow of the dropdown menu takes up valuable realestate where the field name is being displayed.
Question: Is there a way to turn off those individual datasheet dropdowns and get rid of the arrows so that the form doesn't have to be redesigned, due to increased column width considerations which the down arrows cause, just to display the full field labels as they always have been in Access 2003?
if a relevant user opened the db. All well and good, except they then wanted to be able to see the Access link in the taskbar (which SW_HIDE doesn't do) - so I changed it to SW_MINIMISE and they were happy again until..They then realised (and it was a surprise to me as well) that the right click context menus used to filter and sort continuous or datasheet forms were no longer available to these users - nor was the context menu for datasheet columns to freeze or hide columns - see attached.
I've experimented with a number of options and these context menus are available if ShowWindowAsync is not called or if called with SW_HIDE, but not for SW_MINIMISED, SW_SHOWMINIMISED, SW_SHOWMINNOACTIVE, SW_SHOWNOACTIVE.
Why the shortcut menus are not available when the Access window is minimised? The requirement being that the context menus are available to all users the Access link appears on the task bar for all users the access window is hidden for some users.I should say that due to hiding/minimising the access window all forms are popup and modal.
I wanted a Switchboard page in Access to open automatically when the database was opened. I've done that but, as I did it, while in the Tools/Startup to set Display Form Page (in this case a switchboard page but it's not opening full screen and I ow have no way of editing anything), I stupidly de-selected the options there... Display database window, Display status bar, Allow built in tool bars allow toolbar/menu changes.
Now I have lost the tools Menu, the View Menu and others (where one sees, File, View etc at the top of the window) and I can't work out how to get them out. I can no longer view my Access pages in Design View so I can't amend the any pages.
Can anyone tell me how to get my View and Tools menus back on my Access app window?? It's a bit of an emergency... been up all night and have to hand this in as coursework at uni in about 3 hours and I've screwed up right at the end and can't do the last couple of things before putting it on a CD for my tutor to mark.
Help!
I'd also like to know how to get it to open the first form at full screen.
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
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 have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
I have two questions related to deplying an Access project I have been working on.
1. I started developing the project in Access 2000, but midway upgraded to Office 2003 and so the remainder of the project has been developed in Access 2003. Things seem to be fine, except that in the top most title bar, after the project name, there appears the following text:
xxxxx: Database (Access 2000 file format)
where xxxx is the name of the .mdb file.
Why is this appearing and should I have done something or do something to make it a Access 2003 format?
2. I am at the point of deplying the db to a small group of users (about 5). Some of them may have Access 2000 or Access 2002. Should I be doing something in particular to make sure things work in their machines. Any pointers to what may be problems or what I should do will be much appreciated.
A few years ago I’ve made an access database on access 2000. The problem is that now I’ve installed the office 2003, and I can’t make the database work properly.
At first says that are missing those files: “tshoot.ocx”, “msioff9.ocx” and “msowc.dll”; so, I’ve copy them from another computer using office 2000 and now only complains about “msioff9.ocx” saying that my database contains a reference incomplete to it.
Is there no other way to convert my database do work properly with access 2003? What can I do?
I have an Access db that is going to be shared by two different users. One user has Access 2003 and the other has Access 2002. Will there be any problems using this setup if both the users are accessing the MDB file at the same time?
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
