12-15-2010 12:02 PM
I was intentionally vague about my issues because I didn't want to hijack the thread. Most of them can be found in other posts and many, many more in ITToolbox which I don't use anymore. But I'm not interested in paying a programmer to fix Sage problems, I'm interested in Sage fixing Sage problems. I'm also interested in Sage doing some minimal QA on some issues that clearly should have been caught before released.
12-15-2010 12:11 PM
No program meets the needs of all people. And virtually no program of any size at all is absolutely bug free. It may be that if I was on a current version of SLx, I wouldn't have the problem. It's just frustrating to have a task that I need to complete and not be able to do it because of something that should work. Manually changing three fields in 8,000+ contact records would not be much fun.
Thanks for your input guys.
12-15-2010 12:59 PM
I can imagine you are saying that. Manually changing that much data is no fun at all.
I am developing in SLX for almost 13 years now and I wrote many SQL scripts for altering
data myself. I've used the WG Admin quite often for that purpose, because most of the time
that's even faster than the Replace Data wizard execution.
Or I would just write a VB script to handle it.
I agree that the Replace Data Wizard should be fixed, because an administrative user should
have a simple tool to work with.
12-16-2010 09:57 AM
Unfortunately at minimum you should be on 6.2.6....
I'm interested in your statement 'all of a sudden' it stopped working...did it ever work in 6.2.3? and Now it doesn't....or did you upgrade to 6.2.3 and now you can't update stuff.
12-16-2010 11:37 AM
12-16-2010 11:59 AM
A - Are the fields in question in 1:1 and/or 1:m custom tables?
B - Are the fields in question custom fields added to the OOTB Slx provided tables?
12-16-2010 01:04 PM
The table in question is linked 1:1 to the Contact table. I don't know about the other; maybe you can tell something from the attached screen shot of the files.