ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> WO issue backout
http://www.istechforum.com/YaBB.pl?num=1222275550

Message started by cathyh on 09/24/08 at 09:59:10

Title: WO issue backout
Post by cathyh on 09/24/08 at 09:59:10

When using this program to back out of an issue, displaying a second transaction after the first is backed out of does not refresh the work order field. This has always been the case and I have told people using this that they have to exit the program completely if they are doing more than one backout with different WO numbers. But of course I just had one forget to do this, and it did some very weird things.
Couldn't this be fixed?

The flagging of back out transactions is great, by the way.

Title: Re: WO issue backout
Post by JEMM on 10/01/08 at 18:38:23

This issue has been confirmed and fixed.

Title: Re: WO issue backout
Post by kevind on 10/02/08 at 07:27:55

Mike,
Your "This issue has been confirmed and fixed" message is much appreciated.

Now you can also include a LINK (http://www.istechsupport.com/bugtrack/view.php?id=4)to the official issue and resolution!! ;)

Title: Re: WO issue backout
Post by kkmfg on 10/02/08 at 07:48:33

Yeah, I'm excited. The bug tracker seems to be working out pretty well so far. Of course, the real test is the test of time.

Title: Re: WO issue backout
Post by cathyh on 10/03/08 at 14:55:09

How does one go about getting the fix?

Title: Re: WO issue backout
Post by Lynn_Pantic on 10/04/08 at 09:04:46

I will get a patch file posted this weekend. I have considered posting the fix as a linked file on the bugtracker when issues are resolved, as there is a way to attach upload files to issues but the concern is, as time goes on, people will download those fixes when they are not updated to the correct version, or they will load an old "fix" that predates a current update or something like that. Mixing programs between different versions can cause problems and this would make it extremely easy to do. Feedback, please.

Title: Re: WO issue backout
Post by GasGiant on 10/04/08 at 20:10:52

I'd suggest just posting a general link to the updates and patches page, not the patches themselves.

Title: Re: WO issue backout
Post by kkmfg on 10/06/08 at 04:36:52

It's worth noting, however, that the istech status page has links to updated programs and there is no protection from someone downloading those files and installing incompatible copies on their system. It's still a bit safer than posting program fixes on the bug tracker itself.

Ideally, and this is a totally hypothetical scenario, it would be best if there were some sort of updating agent which had access to the most recent version of every program and could "auto update" a Classic or Evo installation to the newest version. Of course, this is really easy so long as the only change is downloading a newer copy of a program executable (be it a .RWN, .RUN, or .EXE). Sometimes the database has to be upgraded and that would throw a bit of a complication into things. It should still be doable. Of course, such an auto updater would need to be authenticated so that only registered, paying customers could use it. Still, I think this could be a decent idea as it would help to ensure that the maximum # of people are up to date. However, a potential snag is that currently people sometimes keep away from the bleeding edge updates because they are afraid that something may have gotten broken. As such, an auto update system really only works if you trust that the newer version really is better than the one you already have.

Title: Re: WO issue backout
Post by kevind on 10/06/08 at 06:24:58

I agree with Colin (GasGiant). This way you can manage the patches as you always have.

Title: Re: WO issue backout
Post by GasGiant on 10/06/08 at 06:25:25

Hopefully I can say this strongly without sounding like a jerk...

We are not "typical" software users out here. This is an enterprise software system and most of the users here should either be IT or multi-hat people who realize that they are working with an important piece of backend software. We should be able to handle the task of reading the updates page carefully and understanding what we should be installing or patching based on that. I for one do not want to use any kind of auto updater. I want to decide what to update and when so that I can assess risk vs. benefit. A big part of what I watch on the forum is what problems crop up and what features change in updates so that I can assess my own company's readiness to adopt patches and updates.

Now, if you do think I'm a jerk, don't worry, you're in good company ::)

Title: Re: WO issue backout
Post by RPCAdmin on 10/06/08 at 06:33:58

Colin,

I absolutely agree - I would much rather have control over what updates and features are installed (one of the reasons I haven't turned or EVO notes or links yet). If I screw up an update, I have the forum or Lynn, Allen, Mike to help me get it straight. (and of course the wonderful daily backup)

Title: Re: WO issue backout
Post by kkmfg on 10/06/08 at 06:57:17

Believe me... I, for one, would be a really hard person to truly offend. Just look at some of my posts on this forum even... I'm quite blunt a good bit of the time.

I see your points about an auto updater. I think that I even mentioned some good reasons why the use of an auto updater could be problematic. Of course most people here should be pretty knowledgeable but I'm not sure if every company that uses Evo or Classic has a technical person. If the world were perfect then the ability to auto update (or, like windows update, pick which updates you want) would be helpful. The biggest problem is that some updates break stuff that used to work or otherwise cause havok in the system or change the way things work. This makes it imperative to fully understand what an update will do before you apply it. It's nice to hold back a while and watch the weeping and gnashing of teeth instead of leaping into the fire yourself.

Title: Re: WO issue backout
Post by Lynn_Pantic on 10/16/08 at 18:11:26

Patch posted to www.istechsupport.com/status.php