Oh! I feel really dumb! You mean the paranthesis "(" & ")"! Gotcha. I'll try removing that, but how will it send those values to the function? Maybe I'm confusing myself.
Yes, I noticed the sub w/in a sub after I posted and changed it to its own section. Still got same error.
I'm not sure what you mean by it still has the ( and )?? Are you saying that the commas still mean and?
Okay it's kinda long though! I'm just testing it with Avulsion first... What I have in the If section for Intrusion works fine. I guess I can just go back to typing it for each IF if nothing else. The highlight red is where I'm getting the compile error.
Private Sub...
Type mismatch on Forms!Avulsion
this is what i have
Function checkToOpenNewRec(FormName As Form, stPatientID As String, stDate As String)
FormName.SetFocus
If IsNull(FormName!PatientID) Or IsNull(FormName!Date) Then
DoCmd.GoToRecord , , acNewRec...
Not sure...
I haven't created functions in a long time.
How do I pass the variables & call the function?
Sub
dim stFormName
dim stId
dim stDate
stFormName="Avulsion"
stID = Me!ID
stDate = Me!Date
checkToOpenNewRec (stFormName And stId And stDate)
End Sub
and then the function...
I have a button on form1 to open another form. Upon clicking the button, depending on information in the form1, it will either open form2 or form3. Open opening either form it filters to match specific form1 fields- if no matches it needs to create a new record with those fields pre-filled in...
I figured what my problem is! I've found out that the error message
shows up when trying to set my strings to a null value (the null would be from a filter that didn't return anything). I've fixed the problem by using the "IsNull" in my if instead of evaluating two values.
Dim stDocName As...
So far I can filter fine from one form to another. I'm using the following code:
Private Sub cmdOpenTraumaFormFrDateForm_Click()
Dim stDocName As String
Dim stLinkCriteria As String
stDocName = "TRAUMA_TOOTH_INFO"
stLinkCriteria = "[Date]=" & "#" & Me![Date] & "#" &...
I fixed the errors by applying a patch from:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q286026
The SQL Server driver in Visio was thinking I was using SQL 7 and not 2000. The patch fixed this problem.
I fixed the errors by applying a patch from:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q286026
The SQL Server driver was thinking I was using SQL 7 and not 2000. The patch fixed this problem.
I reverse engineered an SQL 2000 database into VISIO (need to create some auto-update scripts) and am receiving the following error for 13 different data types (eg: char, int, bit, timestamp, nchar, varchar, etc.):
"The user defined type name is a reserved word in the target DBMS"...
I reverse engineered a database and I need to produce some update scripts. My problem is, when I go to produce the update/generate - VISIO does an error check and produces physical errors stating "The user defined type name is a reserved word in the target DBMS" for 13 different data...
Go to the menu and select "Database->Reports.." and there should be a Table option to select to create a report. It is a Wizard and will walk you through the steps.
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.