Well maybe I was being dumb after all. After many gyrations yesterday, when that workstation came up today and processed its first batch, we were prompted for the new printer. Yesterday I had uninstalled the old printer from that workstation, removed it from the network, restarted MOM, etc. But MOM never gave me opportunity to point to a new printer.

For anyone who finds this post down the road - at this point my best guess is you will need to remove and unistall the old printer, then restart the workstation. Then hopefully MOM will prompt you for a new printer when it is called on to print to the old one that you removed. Be sure to light a candle and scatter some chicken bones first.

Here's the deal: We would like to switch the label printer we use for 'drop ship orders' and batch catalog requests. I can't find anywhere to update the printer path in MOM - to tell it to use a new network printer for these tasks. Can someone HEEEELLLPPPP????

Thanks,

Ross Walsmith

Kantola Productions

Here's the deal: We would like to switch the label printer we use for 'drop ship orders' and batch catalog requests. I can't find anywhere to update the printer path in MOM - to tell it to use a new network printer for these tasks. Can someone HEEEELLLPPPP????

Thanks,

Ross Walsmith

Kantola Productions

For MOM to recognize authorize.net info in the import file all of the auth net fields have to be filled out properly.

This is really interesting! Does this mean an authorized trans can be imported from authorized.net with the trans code captured? And with that, could it be reversed for a return without having the CC number available for processing the return??

Ross Walsmith
Kantola Productions

Forgot to add - on the subject of ODBC drivers, I found that when I attempted to create an ODBC DSN connection to the foxpro files, when I selected the preinstalled Fox ODBC driver, windows prompted me to download the latest driver from MS.

Go to the windows control panel, find ODBC connections, add a new system DSN and when you select the FoxPro driver you may be prompted to download the latest. Lather rinse and repeat with the lates driver to create your DSN. THen, within Access, specifiy that you want an ODBC database. That will display a list of DSN's including the one you just set up - select that one and you should be good to go.

I hope this helps the original poster who's trying to connect - I can go into more detail if needed.

I also wonder if there's a better driver that I could use which would help with my SQL issues? Suggestions anyone?

AFAIK, ODBC comes with Windows, but as David said you need the driver for the database format MOM uses.

MS has Express versions of its programming languages available for free download. I think they can access ODBC data sources if you have the aptitude and inclination to go that route.

This is my second attempt at a reply here - the first went AWOL - let's see if this one works.

I'm also new to MOM and interested in reporting too. I've been fiddling with Access over the last couple days, and have made some reasonable progress. I've had problems with the SQL though - first I can't sort by aggregated columns, and second my attempt at a Union statement failed in the 'Unioned' SQL - it reported finding a missplaced 'Order' clause because it misinterpreted the cms.order column as being a SQL clause.

It would be really helpful to get a discussion going with other MOM users who are using Access for reporting. Maybe we could share reports?

Thanks,
Ross