From: Michael H. <mh...@it...> - 2009-05-14 21:37:11
|
This is interesting, as the questions seem to be revolving around old versions working and new versions not working! We haven't ever seen any problems either way, but we do things pretty simply around here. My suspicion would be that there is either a problem in the upgrade process or the way the data is being interpreted within the app and/or by the end user. (Perception is everything! :) So we still come back to the original question of whether the patch is valid...? Anybody out there take a good look at what the patched code does vs the current (and/or old) original code? Thanks, Michael On May 14, 2009, at 1:20 PM, Dieter Simader wrote: Take a statement from a bank and compare it to the reconcilation screen. It will match your statement. The reconciliation process in previous versions did not match because it was an ongoing process. With the new version you can go back and also reconcile past statements. On Thu, 14 May 2009, Michael Hasse wrote: > I beg to differ Dieter. It may work as the programmer who wrote it > intended, but if there is sufficient confusion as to the manner/means/ > mode of that "working" to prompt other people to rewrite it and for > the end users to believe those re-writes have "fixed" it, then the > average person would have to conclude that the original code is > broken, at least insofar as it does not function in the real world as > the user expects it to. And when you come right down to it, spec or > no spec, it's really the users who ultimately have final say as to > whether something works. > Believe me, I'm not casting aspersions against your code. I know > you're very talented and if you say it works then I'm sure it does! > But it would be of benefit to all if some understanding were reached > as to why everyone else believes it doesn't. I would hazard to guess > that examining exactly what that patch does would be a good first > step. > The second step would be to either incorporate the patch if it's > not actually harmful, or to broadcast to the world exactly why the > patch is, in fact, a Thing of Evil which will wreak havoc upon the > applier's SL universe. > Unfortunately the current situation creates doubt in everyone's > mind about both products and that doesn't help anybody. :( > > > Thanks! > > Michael > > > On May 14, 2009, at 9:22 AM, Dieter Simader wrote: > > The reconciliation process works as intended. If there are prior > reconciled transactions showing up then the reconciliation process > was not > done correctly. > > Before applying a patch users should investigate why these > transactions > show up. If it is a bug it will be fixed but if it is simply a user > error, > well, then fix up your own f'up. > > > On Thu, 14 May 2009, Armaghan Saqib wrote: > >> This patch is now available on ledger123.com's git repository at >> http://github.com/ledger123. Kindly test it and let me know any >> issues. I shall be happy to immediately correct any other issue. The >> repository version has been synced with sql-ledger-2.8.24. >> >> If you are not comfortable with git, email me offline and I shall >> send >> you the patched files. >> >> Regards >> > > ---------------------------------------------------------------------- > -- > ------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! > Your > production scanning environment may not be a perfect world - but > thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW > KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > > > ---------------------------------------------------------------------- > -------- > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! > Your > production scanning environment may not be a perfect world - but > thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW > KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > ------------------------------------------------------------------------ ------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ sql-ledger-users mailing list sql...@li... https://lists.sourceforge.net/lists/listinfo/sql-ledger-users |