Results 1 to 2 of 2

Error 13 type mismatch after windows and office update

  1. #1
    kornowka is offline Novice
    Windows 10 Access 2016
    Join Date
    Oct 2018
    Posts
    1

    Error 13 type mismatch after windows and office update

    Hello access users, did someone of you have similar problem and now the solution fot this case:


    After Windows & Office Update (Windows 7, Office 2016) my tool stopped working properly on some computers.


    It means that VBA macros running correctly only on the computers which was not updated yet.


    Shortly about the project


    there is 2 databes connected between each other, one of this tool was created in order to read custom information from .txt reports and count specific values
    to automatically added recordsets, based on ADO library.


    Everything works good till the moment, when macro need to count summary values for one table.
    It goes like that:




    Dim rsTable1 as New ADODB.Recordset
    Dim rsTable2 as New ADODB.Recordset


    rsTable1.Fields("SumToPay").Value = Round(rsTable2.Fields("Fee").Value +_
    (rsTable1.Fields("Amount1").Value - rsTable2.Fields("Amount2").Value * rsTable2.Fields("Amount2").Value,2)




    After Office Update MS Acces showin well-known error 13 data mismatch. At first I was thinking that there is a trobule with the reports (wrong path dedicated),
    so I repeat the process, but seems that reason must be different.


    What must be done to solve the issue? Is it possible that library is switch off?
    or maybe the math construction need to be write again or there is a on little mistake, that was not a problem for various versions of Office?

  2. #2
    Ajax is online now VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    6,131
    it may well be an update issue, but at the moment your code does not make sense. You create two recordset objects, but have not assigned a recordset to either of them

    assuming there is missing code which does the assignment you could try referencing them differently

    rsTable1!SumToPay= Round(rsTable2!Fee +_ etc

    type mismatch implies trying to assign text to number or visa versa which is a data issue - perhaps one of the values is null

    with regards libraries - easy enough to check - go to tools>references - is one of them missing?

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 3
    Last Post: 08-10-2016, 10:26 AM
  2. Type 13 (Type Mismatch) error
    By sdel_nevo in forum Programming
    Replies: 5
    Last Post: 01-22-2016, 09:01 AM
  3. type mismatch after update
    By cpbittner in forum Forms
    Replies: 3
    Last Post: 03-03-2014, 10:10 PM
  4. Replies: 7
    Last Post: 07-24-2013, 01:01 PM
  5. Replies: 1
    Last Post: 05-11-2012, 09:59 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Tech Forums: Microsoft Office Forums