Re: [Emerald] Emerald 2.5.263 / 2.5.267 - Type mismatch

david leigh ( (no email) )
Fri, 12 Mar 1999 11:12:26 +0800

Hi Anabel

I've had the *exact* same problem with Emerald as well. This occured on a
database that had been set up by IEA and using the 2.5.263 client - with the
same errors happening on the 2.5.227 client. I have been discussing this
with IEA over the last weeks but they have gone a bit quiet (hint hint
guys....waiting for your call or email).

You might want to go back to the MBR in question and reopen it after
attempting to create the second sa. Although it doesn't show immediately, if
you close and then re-open the account window it will now appear there. You
can delete it at this stage and it goes without complaint.

David Leigh

>When creating a sub account, Emerald 2.5.263 brings up a 'Type mismatch'
>error when you save the record. The record does get saved but one cannot
>run the batch-out process because the same error occurs at that stage.
>I checked the masteraccounts table and found that it was inserting a
>null character in the maexpiredate field. Anyone had this problem? Is
>there a fix for it? I've also tried Emerald 2.5.267.
>For more information about this list, including removal,
>please see

For more information about this list, including removal,
please see