I assume you have a form that does not have a RecordSource but does have unbound controls on it? If so, you write code to set the value of the controls to the values in the recordset.
LDBs hang around because someone exited the system in an unusal way. You can just delete it.
Check out the CompactDatabase method for help on you other questions.
Is this part correct: [regname] = " & """" & RegionName & """"
What's with all the double quote marks? Are these actually stored in your tables?
I assume there is a table with many columns here:
Dim fld As Field
Dim rs As Recordset
Set rs = CurrentDb.OpenRecordset("your table name here")
rs.MoveFirst
Do While Not rs.EOF
For Each fld In rs.Fields
If Len(Trim(fld.Value)) <> 9 Then
'....do something to let...
Here's a start:
Public Sub DynamicForm()
Dim frm As Form
Dim ctlLabel As Control, ctlText As Control
Dim intDataX As Integer, intDataY As Integer
Dim intLabelX As Integer, intLabelY As Integer
' Create new form and set its record source.
Set frm = CreateForm...
Pass the client name to frmAddClient using OpenArgs (see DoCmd.OpenForm) and set the proper form control in the OnOpen event.
Enter the other info and store the ClientId in a global variable using the AfterUpdate event. Close the form.
In the Activate event of frmAddNewJob, do a...
Query2 resultset is a subset of Query1. The added "where" condition should make it run faster.
Try this for a speed fix... create a dummy table in the data database with 1 field (name it what ever you want). Create a global recordset variable in a module of your application...
A little more info: are you trying to refer to it in VBA from a mainform? If so you can get to the subforms underlying recorset:
Private Sub Form_Current()
Dim rs As Recordset
Set rs = Me.<subform name>.Form.RecordsetClone
....do what you want
End Sub
"You can also use the recordcount, if a value is returned then your set is open, if an error occurs then it is closed."
No offense Harpz but that is not a very good solution. Not only do you incur the overhead of error handling by doing it this way, you would probably catch heck from...
Upon some event (i.e. form_current, acctnumber_afterupdate), set the RowSource property of the combobox to a query selecting the correct attorneys and then requery the combobox.
"Record too large" indicates that one of the records you are creating is breaking the 2K (for Access 97) or 4K (for Access 2000) limit. A record in Access can't span across multiple database pages.
202 fields probably indicate that the table needs to be redesigned. Either that or...
Racer, I think you missed the jist of the topic. Anyways SR, add a button next to your textbox that will kick off the following on the click event:
Private Sub Command10_Click()
Me.Filter = "[Value] LIKE '*" & Me.Value & "*'"
Me.FilterOn = True
End Sub
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.