Search results

if you mean running the code behind the event procedures then you can. Like normal procedures or functions you can call them by their name, eg: Private Sub Command0_Click(): Call Form_Current: End Sub Private Sub Form_Current(): MsgBox "You can call this sub!": End Sub clicking the Command0...

if you use SendKeys to access menu items then you will have problem if the menu bar/toolbar is hidden because the line will not trigger the action of the menu. it's better to use DoMenuItem, if that's the case. however, RunCommand already replaces DoMenuItem. i find the new method easy and...

do: Private Sub MovButon_Click() Me!EditBox = Me!ListBox End Sub

i can see that you are using the strSource as OPENARGS argument to the OpenForm. am thinking that you will assign this during the OnOpen of the form as the form's recordsource. if you do, then subsequently, you can: Forms.RecordSource = strSource Forms.RecordsetClone.RecordCount = 0 then Msgbox...

i can see no error in your code since you also stated that it all worked fine previously. however, i would like to suggest changing the SENDKEYS line to: Docmd.RunCommand acCmdRepairDatabase 'repair database Docmd.RunCommand acCmdCompactDatabase 'compact database this is more natural...

try this: Case "LastUsed" strFieldValue = PutSpaceInDate(Nz(rstClient!LastUsed, Date()))

Me!ControlObject.Visible = Not(Me!ControlObject.Visible)

it's working on my copy. i tried different formats, even passing the parameter as string. are you sure?

here's a fxn: Public Function PutSpaceInDate(dtDate As Date) Dim strDate As String Dim intLoop As Integer Dim strSpaced As String strDate = Format(dtDate, "ddmmyyyy") For intLoop = 1 To Len(strDate) strSpaced = strSpaced & (IIf(strSpaced =...

not sure if this is what you mean. however, you can change the numbers (basing on your example) to the proper fields on your form. Validity = iif((100 <= 177 and 200 >= 177) and (177 mod 5) = 0, "Valid","Invalid")

i downloaded your .mdb but their is a problem when i open it or should i say, i cannot open it. i will welcome if you send another copy!

you can send it to my mail!

go to TOOLS >> ACTIVE X CONTROLS. click register and look for the .ocx of the calendar. adding references only adds references, the control part of it (active x) should be registered separately.

D is double-precision as in type DOUBLE!

you can format the field: eg. Format([NumberText],"00"). now the 0's depends on how many digits your highest number has. if you only have <99 then "00", else if > 99 and < 999 then "000". so on and so fort, i know you get the point.

okay! i've seen the problem. isn't this the effect of accepting variant as parameter???

here's a function: Public Function GetNumericInString(strText As String) As String 'extracts all numeric from the string Dim intLoop As Integer Dim strResult As String If Not (IsNull(strText)) Or strText <> vbNullString Then If InStr(1, strText, "P.O."...

i believe that either way you put it (first or end of the character), you should check if the comma is existing. using kaspi's example, if the user choses "3,". you'll still have to check if comma is the last character. what about "4". using pat's example, if the user choses ",2". you'll still...

i've sent an example through your mail!

if i want to clear the contents of all the controls in a form or any other objects that can hold control (tab pages, option group, etc.), i do this routine: Dim ctl as Control On Error Resume Next For each ctl in Me.Controls ctl.Value = Null ctl.Caption = vbNullString Next i use on...