I don't know about AIM*, but this exact thing can be done on Aspen IP.21. (Actually, in IP.21 it is quite easy to rename points, or reassign their collection sources.) One of these days I'm going to try it on the legacy hist... Corey Clingo BASF Barry Heap <BHeap@xxxxxxxxxxxxxx> Sent by: foxboro-bounce@xxxxxxxxxxxxx 03/09/2010 05:45 PM Please respond to foxboro@xxxxxxxxxxxxx To "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] AIM* data accessibility Hi Matt, Your logic sounds so reasonable ... unfortunately I don't think it is possible. AIM* goes to a great deal of trouble to ensure that the data integrity is not compromised in any way (and this is definitely playing with the integrity). You will note that the configurator specifically does not allow you to edit the point in collector field - and I doubt using text files will work either. If you try to modify the point in collector via a batch file I am pretty sure it will bounce an error (point already exists??). If you could get it to work, I would like to know because I have some fractured databases around that it would be nice to fix. You can easily test this - just create a dummy block (with some dummy changing data) and a historian point, let it collect for a day or so and then move the block and edit the collection point. You will need to force delete the point when you are done, but it will prove the point. Or maybe someone can try it for you on a lab system. If I had a system to play on, I'd try it ... but I don't think it will work... Regards, Barry Heap _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave