Hi All,
I am learning heaps and constantly wrestling with access, this is a good thing. However at the moment i recently added tabs to my form to restructure the appearance and content and thus far i am happy and its working fine. Except that moving the mouse cursor accross the from causes controls and textboxes to flicker / refresh. I find this annoying and given all the effort going into the presentation of the application i have done.
Is there anyway to eleviate this, is there something i have done wrong perhaps.
I wish to host various controls and inputs from other tables on the other tabs. Will this complicate things or should 1 form with its Tab controls be particular to 1 table........ or can / should a form serve as an input or display to several tables? Is this a bad database practice?
thanks for any assistance you may be able to provide.
I m trying to create a form with tab controls but it keeps on disappearing in the form view but showing up in design view. Even when I delete the tab control and drag existing fields onto a blank form it is still not showing up in form view but showing in design view.
I have created a form to summarize sales data for the past two years. The form uses a tab control with 12 tabs(By Region, Country, State, SalesRep, etc.). Each tab has its own subform link to its own query(Each query has two subqueries so that I can get percent difference). The subforms also have total fields at the bottom in the footer. The sales data comes out of two differnt tables so I can compare this year to last year. My problem is speed. It takes about 35 seconds for the form to open. Is there a smarter way to do this.
I was just converted from 97 to 2003 this weekend. I have a query set up that links a field to a form to get the date entered in the form into the query. For example if I enter 12/31/04 on the form and run my query it is put in the field 12/31/04. But in 2003 it is just blank. The formula I used in 97 is
StartDate: [Forms]![Cash Flow]![Start Date]
Is there something new I should be using to get that to pull in?
I am new to ACCESS, I have some experience with SQL, VBA and RDBD having been trained by ORACLE
The attached tables come from a RB I am making, I can run the SQL and it works, I have failed to create form or report tha enables users to simple use a button to invoke that code.
Several people have sent answers but I have not made them work, the tutorials that I have looked do not explain with simple examples that I can follow.
I am using Access 2003 and I am having trouble with a Combo Box on a form.
I had a combo box (based on a table), storing the choice in a field in the query and underlying table the form is based on. Everything was working fine, until... I altered the form based on a query. Now when you make a choice from the drop down list you get an error bell and nothing happens.
I am using John Big Bootys Dynamic Search Form (built in Access 2003) as it totally met my search requirements, however when typing anything into the search box it is realy slow, taking several seconds for each letter to show in the box.
This has always been a problem now and again, however some of us have upgraded to Office 2010, (although still using the 2003 built Db as we won't move to a 2010 version Db untill March next year) and now the problem is even worse that ever. Everything else seems to work really well except for this search function, however it is the search function that is used more that anything else.
When I import a form with the Navigation control on it The following attributes of the navigation buttons are changed to #FFFFFF:
Hover Color, Pressed Color, Hover Fore Color, Pressed Fore Color
I was hoping to be able to automate the updating of customers databases by sending them a database which would export the required objects rather than the whole front end database. I can think a way around this by including code in the form so that it changes the attributes to the desired values, which are:
Accent 1, Accent 1, Background 1 and Background 1. But I would rather not have to do that.
It is interesting to note that the Border Color attribute is not changed on importing.
:confused: i am using MS Access 2003 on WinXP. i have attached my sample database. when viewed in form view, notice that the form will flicker on mouse over. why is this happening? is there a solution to solve this annoying problem? please explain in details how i can solve this problem as i am new to access. thanx in advance :)
Hi I am using the following Code on the OnCurrent Event of my form. The Problem is , in Access XP or 2000 it works Great but in Access 2003 it starts flickering, unless we bring the cursor to any field of the subform
Private Sub Form_Current() On Error GoTo Err_Form_Current
If Me.RecordsetClone.RecordCount > 1 Then Me.ScrollBars = 3 Else Me.ScrollBars = 0 End If
Exit_Form_Current: Exit Sub
Err_Form_Current: MsgBox err.Description Resume Exit_Form_Current End Sub
I'm having a problem with what looks like a form refresh.
My form has a single drop down box, when that's updated, the whole form is visable and resized etc.
Depending on the criteria in the dropdown box, up to 20 text boxes are updated using a DLookUp. Everytime something is done (like ticking a checkbox or pressing a button) in the form, the 20 text boxes blink, and it's really... really... REALLY annoying me and my colleagues!
I've tried converting them to labels and using code to update them, but that didn't seem to do the trick.
I could put the info in the query where the form gets its data, but the form is for data entry, which i cannot do with a linked query.
I'm supporting some Access/VBA code which includes the following behavior:
When an update is made in a (linked) child form, the current date/time is written to a textbox on the main form via
Me.Parent!txtMod = Now
Likewise, the BeforeUpdate event of the main form updates the same field (and then does a bunch of form validity checks, possibly followed by a Save).
When we upgraded to Access 2003 from Access 2000, a problem erupted:
When the user returns to the main form (by clicking on any control outside the subform), the following message is issued: "This record has been changed by another user since you started editing it (etc.)..."
At this point the user must choose between "Save Record", "Copy to Clipboard" and "Drop Changes".
Conceptually, I see why this is happening (though I wonder why Access 2000 didn't flag it). The subform is the "other user". When the main form is returned to, it is "Dirty" (unsaved update), so the main form's BeforeUpdate event fires, and attempts to update the field again (Me.txtMod = Now). Since there is a pending change to the field, an error dialog pops up.
As a quick fix, I replaced the code in the subform with a flag ("Hey, I've been updated!"), which the main form checks on the Exit event of the subform control. But that seems a horrible solution. Surely there's a better way?
Notes:
1. It would be preferable to have the timestamp updated right away by the subform, though having it updated when the subform loses focus is better than nothing.
2. Since a subform is a control from the main form's perspective, I'm surprised that a change to that control doesn't render the main form "Dirty". I guess from a database standpoint it makes sense (the form's table isn't getting updated at all; just the subform's). But then, how does the main form know that the subform has been updated?
3. I tried catching the error via Form_Error. I can make the dialog not appear via "Response = acDataErrContinue", but unfortunately it defaults to dropping the changes (old and new), rather than saving the new.
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 am looking for a book or poster or something that can show me all the access controls and what they do. My VB.NET version came with several posters. I have looked at many books but can not find one that enumerates and explains all of them. I would also like to get similar information for the Active X controls included with access. Thanks
Hi all, I have been given a database from a small business who just want some menial report editing. Their problem is the supplier of this simple access database has disappeared and in over a year of reporting the problem has not resolved it.
The database is locked interface-wise, i.er. if you load you cannot access tables, queries, reports etc. I was wanting to know how you do this. If the database is passworded I have a revealer, but actually getting to the edit area seems to be the problem at the moment.
I have two subForms on separate pages of a Tab Control on a main form. I want to create a Textbox on one Form to display the month of a Date field on another form, using DatePart.
Using the On Current event, this works ok, if I have the 'other' subForm open in its own right, but I get message telling me it can't be found if i don't. Here is what I have...
Private Sub Form_Current() If Not IsNull(Forms![Reviews]!SelectLessee) Then Dim revDate As Date revDate = Forms![subReviewPEST]!DateOfNextCreditReview Me.Text118.Value = DatePart("m", revDate) End If End Sub
What syntax do I need, or how then can I access the control without having the subForm open itself, by getting to the page on the tab control, then to the control on the subform...
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.......
