Type 13 (Type Mismatch) error

[sdel_nevo]

Hi Everone

I have an issue with athe dcount below, when the code runs im getting a Type 13 (Type Mismatch) when i try to run this dcount


Dim countID As String
countID = DCount("SOIID", "SOIDetails", "WORKORDERID='" & Forms!SOIAdddetails!WorkOrderTXTBox & "'" And LPosition > 0)



this is the code on the form this all runs when a text feilds after update event.

Dim LPosition As String
LPosition = InStr(Me.PartNumberDescriptionTXTBox, "*")

If LPosition > 0 Then
Me.Ends7 = True
End If

If LPosition = 0 Then
Me.Ends7 = False
End If

Dim countID As String
countID = DCount("SOIID", "SOIDetails", "WORKORDERID='" & Forms!SOIAdddetails!WorkOrderTXTBox & "'" And LPosition > 0)


if i comment out this line countID = DCount("SOIID", "SOIDetails", "WORKORDERID='" & Forms!SOIAdddetails!WorkOrderTXTBox & "'" And Private Sub WorkOrderTXTBox_AfterUpdate() > 0) no error is produced


how do i include the variable LPosition as a critria in my dcount?

many thanks
steve

[cyanidem]

DCount returns number, and you declared countID as string and then you're trying to set string to number:
countID = DCount(.....)


Edit:
Actually same problem with LPosition. Declared as string and then:
LPosition = InStr(....)
but InStr returns integer, not string.

[sdel_nevo]

Hi cyanidem

many thyanks for getting back

i have changed countid to single
and
Lposition as integer but im getting the same error

i have also tried double

kind regards

[cyanidem]

Could you upload your database?

[sdel_nevo]

Hi Cyanidem

the most odd thing is happening to this database, when i made the changes above i still got the error messages, when i created a new blank form and copied my code into it everything worked?

i have had this issue recently so what i think i need to do is to cteate a new blank database and try importing all the tables, forms, reports and querys into it.

many thanks for your help its all sorted.

Kind regards

Steve

[Missinglinq]

...when i made the changes above i still got the error messages, when i created a new blank form and copied my code into it everything worked...

Doing this is the first line of defense when corruption of the database itself is suspected, which would tend to suggest that your db was, in fact, corrupted!

Allen Browne has an excellent article on the prevention of corruption, during development and after distribution, that you probably need to look at:

http://allenbrowne.com/ser-25.html

Linq ;0)>