Recent content by bcygan

I had intended to include reports and views but your idea about creating custom Crystal Reports will work just as well. The biggest concerns are entering sales orders, selecting for billing, anything transactionally based.

Essentially we'd like to limit everything in the OE module to one location for one particular user. I've been able to restrict everything else through screen manipulations.

Where is it done? I've checked user maintenance and can't seem to find anywhere to specify location access.

Progression MS SQL 7.6.4b

Is there a way to restrict viewing/maintenance of a location within a company by user? In this example we have four locations within our company, 00,02,17,&31. We want to setup a user with rights to work in location 31 while preventing access to the other locations. Thanks.

We are running PWE 7.6.400b. We generated and posted some Credit Memo's from RMA's in error and I am unsure how to unpost them.

We are looking to add additional inventory classes beyond the standard ABC in the Item Location. I spoke with Macola support and they stated that the ABC analysis and Cycle Count features will stop working. This isn't an issue for us because we don't use those functions. Has anyone else done...

Thanks. I was leaning in that direction but I wanted to be sure that wouldn't have any unintended consequences.

That deletes the entire BOM for one parent. I need to take one component out of hundreds of parent BOM's.

We have a small number of items that appear in the BOM's of several hundred other items. We need to remove these items from all of the BOM's. I know there is a Mass Replacement feature but we are not replacing, just removing. We are running 7.6.400b.

Tried it both ways...I had the problem user try it from a different PC (no success) and had a user who can print try it from the problem user's desk (printed fine). It still looks like it is user related.

Progression 7.6.300b One user has missing lines when printing sales orders. Other users can re-print the same order to the same printer with the same settings and the order will print correctly. This problem appears, at least on the surface, to be entirely user related.

Backorder created successfully

This is an inventory item that we sell thousands of a day. I tried recreating the issue with the same item/customer combo in a test company and it worked perfectly.

I ran an audit trail on both and neither changed recently.