Search results

You need to put that exact criteria in each of the columns that you want to search through. Don't copy it on the same line though. Put it on the first line for the first column, second line for the second column and so on.

I'm a little confused by what you're saying but every textbox has a default value property. Will that take care of your problem?

Do you really need to delete the table and recreate it? Can you just delete the data and then insert new data? If you have to delete the table then use code to first delete the recordsource of the subform, delete the table, recreate the table, and then set the recordsource of the subform again.

Well no, neither of them can add records. I tried using the command you gave me and got an error saying 'Object doesn't support this method.' I also tried Forms!MainForm!Subform.Form.Refresh. Didn't get an error but it also didn't work.

I have two subforms that are related. The first one is a datasheet showing all the records and the other is a single form showing more detail. What I'm trying to do is when the user modifies a record in the single form then have those changes propogate to the datasheet. I've tried using the...

Are you using access 2000 or less?

Does anyone know of a way in access where you can open a modal form that will pause the code from which it was opened. Kind of like in VB where you can do a ShowDialog and then pickup in the code using the result from the ShowDialog.

I like to use DAO in Access and yes, you don't have to setup the connection string. Dim rst as DAO.Recordset Set rst = CurrentDb.OpenRecordset("Table or Query Name")

In the 'Input mask' property of the password textbox type 'Password'

I would base the report on a query or better yet a pass-through query that performs the count.

DatePart("ww",[Date field]) I believe this gives the number of the week. If not look up datepart in help files and it will tell you.

If you're using access security then just create a table like I said at first with their access ID's. Then when the file opens have it look up the form in the table use CurrentUser(). Then run a docmd.openform with the formname in the table.

Give the code in the attached file a try. You should be able to copy and paste it without making any alterations. What it does is test whether the file is an mde file or mdb. If it's mdb then it unlocks everything. If it's mde it locks everything down. How I call it is create a macro called...

You need to create two columns in your query: Column 1: Month([Your date field]) Criteria: IIF(Month([Your date field])=1,12,Month([Your date field])-1) Column 2: Year([Your date field]) Criteria: IIF(Month([Your date field])=1,Year(Date())-1,Year(Date())

If you're using OS such as Win2k or xp pro then you can use this function to determine the user id of the person logged in: Private Declare Function apiGetUserName Lib "advapi32.dll" Alias _ "GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long Function fOSUserName() As String...

lol. Been there. Well you can do this with either macros or VBA. Add mode simply means that the form is opened with the recordsource you declared but without any of the existing records. So with this mode, when you open it you won't be able to navigate between records until you add some...

Just out of curiousity, why do you want the data in the one table to also be in the many table? As long as you have a field in both tables to build a relationship upon then you can create queries that link the two and there you go. That's the beauty of relationships.

In the On Open event of the form (or even on load) use a Docmd.GoToRecord acNew Or if you want it to be strictly a data entry form you can set the form's property to data entry or you can open the form in Add mode.

Well you're right. It let's you do it with text but not with the autonumber. Don't know why exactly. Another thing you could do is break them up into separate forms and for the sub records use a combobox so they can select the correct main record.

I believe I've got it. Creating an input form with an input subform is kind of tricky when there's relationships between the two. Let me see if I can explain this in a simple manner. Let's say you move to a new record in the main form and the subforms naturally requery so they're at a new...