• Phil is 100% correct

    If this is something you did not try and do not know how it will effect the system or how to trouble shoot it if it does go badly I would not try it on a live system ever.   The thing is buidling a new field to hold the data, deleting the old one then rebuilding the old field is a really common practice amoung many SQL programmers that know messing with LIVE data on a system can cause issues.  Rememer slow is SMOOTh and SMOOTH is fast.  The neat thing is you do not have to use Auto index to do it any more.....you can use the workflow to update the HEADER file off the database....so you could:

    1: Copy the data from the table in question to another database....
    2: Delete the field in question
    3: UPDATE/APPLY everything....even logging out of configuration etc is a good idea.../
    4: Log back in add the field back with the new size. 
    5: Copy the data you backed up into the new field. (users can see the data now but you are not backed up)
    6: Build a restore that will OVER Write the XML with Database.....
    7: Run it.....done....

    If you have a really big database or do not have autoindex this should work.

  • CLEAN uninstall

    I have been having an issue with Docuware 6.7 at the office.  I suspect it was from upgrading from previous versions. 

    In the interest in not wasting time trouble shooting the issues I decide to uninstall and reinstall with a whole new SQL etc

    Administration works, the thick client works but the web is blank when asking for \platform and I get a 404 page not found error otherwise...

    I need to know how to cleanly uninstall Docuware.....I want t make a CLEAN install. 

    Craig