We are doing a little housekeeping and cleaning out some old accounts from our system.  In the fat client there is a maintenance option to purge records.  Does anyone know if this option exists in the web-client?  I don't really like getting into the fatclient anymore since we have enabled unicode.  Although...it may not hurt anything just for the purpose of purging records?  Thanks!

Open up the fast client and do it ON the network.......

Ok...thanks!

Ok...so the same time I posted this question on the forum, I also had submitted a ticket to sage.  However, they are throwing more of yellow light instead of a green.  Just wanting to clarify that the issue here is that we are now running in unicode and when I open the fat client I get the nasty little message indicating the risk of data corruption.  I would much rather grind out the SQL to do the account purging but don't really want to unless it is necessary.  Has anybody used the fat client record purge utility to clean out old account records while on a unicode platform...and lived to tell about it

Thanks for any feedback on this issue!

Correction...

I would much rather grind out the SQL to do the account purging as opposed to corrupting data but don't really want to unless it is necessary.

I don't understand how unicode DELETIONS would corrupt data.

Are you saying that issuing a SQL Statement of the form:

DELETE FROM ADDRESS WHERE ENTITYID = @ACCOUNTID

will corrupt data in a unicode database?

Can someone help me out? Thanks!

I totally agree/understand in regards to your statement about deletions not impacting data.  A delete statement doesn't corrupt data - it DELETES it.  The feedback I have gotten from sage is that it COULD indirectly impact other (non-deleted) data by just opening the LAN client.  If this is the case I will need to manually script the deletion of all account related records.  Not really wanting to go down that path unless I have to.

Got it, that makes sense.....

I take it there's no Synchronization involved? You could write a stored proc to delete all of this stuff.....

There is synchronization, we run several remote clients.  I've done a little research and think I know which tables to hit but I'll have to write a utility to pass the SQL statements through the SLX ole/db provider in order to get the changes synched through to the remote clients.  Looking like that is the probably the best route in order to not risk corrupting data :-\ 

Thanks for the feedback!

You run synchronization to remote clients, you are using unicode, and you can't login into the database through the LAN client because you're afraid of corrupting data?

Doesn't make any sense to me at all.

I guess technically they would be considered disconnected web-clients.  By remote client, I just meant that synchronization was taking place rather than a direct connection.  If a database is unicode enabled then the windows client is not technically supported (network or remote).  The basic thing I was after in this inquiry was:

a - whether the purge account records feature was available in the web-client since the lan/windows client was no longer supported in a unicode environment 

b - if it might be ok to use the windows/lan client to delete a group of account information despite the fact that the windows/lan client isn't supported in a unicode setup. 

Sounds like the purge records option isn't available in the web-client and that using this feature from the windows/lan client in a unicode setup is discouraged.  So...I'll write the utility.

Got it, we don't have any web disconnected clients....and I'm a long time LAN kind of guy...