255
I am looking for a MICR solution that is compatible with the new GP Web Client? We can make Mekorma’s MICR product work if a terminal server is setup and GP is accessed via a VPN. However, that pretty much defeats the point of having the GP Web Client. Please let me know if you have any recommendations.
*This post is locked for comments
Charles,
I believe this is actually a more global issue with the GP Web Client. Currently the Web Client does not allow for any ISV product that needs to do anything other than use Dexterity. Typically anything that has to do with printing will fall into this category, although that may be overgeneralizing a bit. The last time that we spoke to Microsoft about this, I was told there is nothing that ISVs can do until Microsoft makes a change to the Web Client to allow them to work with it. There is no ETA that I am aware of.
Thanks Frank - I agree. Per my earlier reply on this topic, "Your workaround (Terminal Server) is probably the best for now, however you can get around the full TS server by having the user that needs to print use an administrative RDS directly to the server, or a LogMeIn/GoToMyPC session to a designated workstation. The designated workstation is probably better since there is no concern with the user shutting down the SQL server accidentally. Everyone else can use the Web Client. This would work in a smaller environment, definitely not one where many users print checks.".
Other than that, since we've come full circle on the initial question, it appears we'll have to wait for Microsoft and the ISV community to work out the interface issues.
Perhaps for check printing, you want to perform that on a non-web client until the ISV's catch up.
You're not hijacking - thanks for the information, and for new ways to use Forms Printer! I just received a response from Accountable sales, and they say that Forms Printer does not work with the Web Client.
I am beginning to realize the incompatibility with the Web Client should not reflect on any ISV, but more with the newness of the Web Client platform and its inability at this point to extend calls to external .dlls and other objects.
Not to hijack this, but if you would like to see how I print MICR with Forms Printer, just send me a PM through the forum and I'll put something together. It is a great alternative if the organization has Forms Printer and wants MICR printing but does not want to invest in additional 3rd party products.
Forms Printer has this ability as I have performed this countless times. It requires the purchase of a third party MICR font (I usually used Adobe for around $30). From here, it is just a matter of formatting a MICR character line and this is dependent on the font selected for the MICR character recognition.
@Frank, I can't reach wellspring software by email or phone at this point, and the latest GP version they reference on their site is 10.0.
@Mike S., Forms Printer does not provide the Magnetic Ink Character Recognition (MICR) fonts, or the capability to embed them in a document, i.e. checks. Forms Printer is excellent for printing to Crystal Reports-fpormatted documents and providing other form and printer redirection.
You may also want to explore Accountable's Forms Printer product. I'm not aware of its compatibility with the web client, but may be another option to explore. If the wait time for compatibility is the same, and the team does not have other form printing requirements, then I would say wait for Mekorma MICR as it has the most robust feature set around check printing in my opinion.
Print Boss is another MICR solution that I've seen work with GP. Not sure if they are web-client capable yet but it would be worth a look. www.wellspringsoftware.com
I'm looking for an answer for this as well. Mekorma seems to be the only MICR product available for GP, so this is causing implementation delays for many of our clients who are anxious to have the web client and also use MICR.
I'm not certain what Mekorma's holdup is, but according to their sales team, "We hope to be web client compatible sometimes in 2014". Not acceptable in my book.
I can see the down side of MICR printing via a web client, that being security. Your workaround is probably the best for now, however you can get around the full TS server by having the user that needs to print use an administrative RDS directly to the server, or a LogMeIn/GoToMyPC session to a designated workstation. The designated workstation is probably better since there is no concern with the uese shutting down the SQL server accidentally. Everyone else can use the Web Client. This would work in a smaller environment, definitely not one where many users print checks.
Charles Ray
CAL Business Solutions, Inc.
#1
André Arnaud de Cal...
292,494
Super User 2025 Season 1
#2
Martin Dráb
231,305
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
