John, I think I found a slightly similar issue reported by you before (although
the error was different: type 1) back in August of 2014.
Apparently, Malware Bytes was causing a problem for you … ? Later, you reported
setting exclusions for the Omsys folders later … but I wonder if that was the
No problem, Scott!
Any information that helps people, is good.
Z
> I hope you guys don't mind .. but I copied the useful bits from this thread
> into
> a post on the Omsys Blog ..
>
> http://blog.omsys.com/2016/04/24/mif2go-and-fm-2015/
>
> That way this info will be available to others.
I hope you guys don't mind .. but I copied the useful bits from this
thread into a post on the Omsys Blog ..
http://blog.omsys.com/2016/04/24/mif2go-and-fm-2015/
That way this info will be available to others.
If anyone would like to provide tips or other info for Mif2Go (or other
Omsys t
Thanks, John.
I will take a look …
Regards,
Z
From: John Sgammato [mailto:john.sgamm...@actifio.com]
Sent: Sunday, April 24, 2016 06:56 AM
To: Syed Zaeem Hosain
Cc: framers@lists.frameusers.com
Subject: Re: [Framers] Mif2Go and FM 2015
Hi Syed,
I have the m2rbook.dll in place.
The issue that
Hi Syed,
I have the m2rbook.dll in place.
The issue that I run into is a familiar one, and infuriatingly vague. It's
a "could not write .mif" issue.
I have seen this before and resolved it for FM12. I expect I can do it
again when I have some time later this week or next week.
In case you want to r
