Has anyone downloaded and used build 374? I am holding off on installing it in our training install as we have been referring back to it for things we did during beta testing, though such use is minimal of late.
Anyway, we have had some issues with printing. Occasionally the logo we added on our forms doesn't print or prints a solid color rather than our logo. I wonder if others have had similar issues and if so, did build 374 address the problem?
I like the idea of a database optimizer, enhanced item lookups, and the GL elimination of year end journal.
I hope to download the update soon and will post my findings. If you have any insights in the meantime, post away.
Subscribe to:
Post Comments (Atom)
15 comments:
I have not installed. I am still on 359. The printing solid color logo thing has plagued us since build 60 or so (yes that long!) I cannot predict it, or replicate it. The error has survived upgrades and new printers/drivers and new workstations. I see it only on POs (I think)
I didn't see a Resolved Programming Issues with this release, that is important to us, anyone find one?
379 is current. There is a list of prog issues, but it's really short, and on a web page only, no pdf.
http://supportcenteronline.com/FileManagement/Download/bf790e80d44f4f8eb18231f2728d1cf0
I can't say anything about the GL stuff, since we don't use it. Speed issues, I can't say I've noticed anything going faster - if anything, switching BOM methods takes longer?
Enhanced lookups is VERY enhanced! And, finally, filtering of inactive parts in at least some screens.
I can't release this in-house yet because they've buggered up something we use (SERVICE icon) and dropped a little turd about rolling service jobs into the SALES function. Have another ticket in for something else - speed entry into jobs started with a template has glitches, but I haven't heard anything yet.
xeyes, Thanks for the link to programming issues, which I too had not found. It sounds like most of the upgrade wasn't addressing specific issues though.
Tom, thanks for the printer issue info. I can't reproduce the problem consistently either, but tweaking settings, adding memory to pc's, changing drivers, and using different printers seems to have made no difference. We have the problem on invoices and packing slips for sure, and I think everything across the board.
Occasionally things print to a different printer than that selected, which is almost always the default for that user, which DBA said others have reported but they cannot reproduce. I was able to create steps to reproduce the printer redirect problem, which they said was helpful, though they provided no contact that update 374 was addressing that issue.
On service jobs: I asked them 4-5 months ago about RMA's and whether it made more sense to set them up as sales or service jobs. Their eventual answer was, for our case with manufactured goods being returned to us for repair, replacement, or restock, that it made no difference. I set up our RMA's as a sales order type.
I think they may try to focus the service functions more to make clearer the distinctions. I like the idea of setting up assets that need regular service in the service assets area and then setting up standing service jobs on a calendar. 10 years ago that would have come in really handy, but I have less need for it now.
The input I got was that there would be no distinction. Service Orders will be gone. They are going to "attempt to make service order functions available within sales". Not soon, and in the mean-time, apparently a continued lack of fixes in that area.
Considering their record to date on things like this, I expect a "better idea" that's irrelevant to the actual need.
Graphics issue sounds like a bug in using a Windows DLL. Nasty to track down - could be delphi, could be windoze (and version-specific), could even be 3rd party function library (if used for graphics/layout) installed by DBA or something else.
We have a printer that switches drawers by itself, in the middle of a print job. A pain sometimes, but can be kind of amusing to watch. Have you checked the printer settings for your reports? Each report can be set to use a specific printer (at least the rtm reports). Might be worth it to reselect the printer configuration in each one you have trouble with, see if that does anything.
To be fair, B has just tracked down a bug in using service order templates, so it looks like some things are still possible after all.
Observation re: 379
Aside from the speed issue, and them deciding that we only needed 2 item statuses (active or inactive), I'm getting the impression the system is losing some stability. I had an issue with the queries totally scrambling the screen contents when I moved around, but I was doing something that is not supported, so I'm not going to get irate. My purch guy did something similar doing something that IS supported, and ended up locking up the system after a few wonky screens (playing with the new select and filter mechanisms), had to three-finger out and restart. No lost or corrupted data that I'm aware of, but a bit unsettling.
We have not seen any real problems with this download. One thing was they went to two inventory codes from 4, and anything that was blank, as most of our items were since that was how the items were imported, was defaulted by DBA to in-active. Since the field doesn't do anything, except for now in 374 it provides some sorting info, its no big deal. Anyway, B provided a command file that re-writes everything as active, and I have a list of obsolete and in-active parts from before which will have to be manually entered, but its short.
Other aspects, the removal lf GL year end, the database optimization, seem ok.
Interesting little tidbit, but probably from an older update - That toggle you can set to indicate a PO line is complete also makes it permanent. You cannot reopen the line without a database "correction" to unset the toggled field.
I checked today. I was able to change PO's back to either printed or open status from closed, and once the PO header is reopened, change line items from closed to open. This worked in versions 366 and 374 without any difference.
We haven't started using 374. I'm going to press the issue today with users, as I want to be prepared to review the next update.
You can change the status, but you cannot edit the receipt activity (which is why you would normally reopen a line). Reopened line doesn't show up in the PO Receipts window. It takes a database change to do it.
Is this blog still alive?
Let's make it alive
I've had issues with the DBA "support system", and would welcome any forum to discuss both features and problems of this software. I know that work-arounds for this program exist, but we need a central place for discussion. If anyone is interested in reviving this blog, I'll check on it weekly, just post your comments...
I am trying to find some actual users of DBA NG and i came across this blog. I am going to be implementing the software at small custom circuit board manufacture and I would like to hear what some actual users have to say about the software package as far as pros and cons. Any responses would be appreciated.
Post a Comment