archiving citadel database from one computer to another dsc

[Kenny_K]

I am trying to archive a citadel databse from one computer to another.  I am able to do this, but it is not archiving as I expected and I then cant view all of my data. I am using the dsc module to record the data with network published shared variables.

As you can see in the pic, I am trying to archive the data from my computer (\\KKREITZER) to a different computer (\\SSEMP).  I have been taking data on the kkreitzer computer for a couple of months now while developing the program and am now trying to move it over to the server.  I named the database the same, ss data, and used the archive function in MAX to transfer the data from kkreitzer to ssemp.  But now when ever i try to access the data from the ssemp, it is logging the data and looking in the ssemp portion of the database, and ignoring the kkreitzer data.

I must be missing a setting to get all my data in one spot so that I can view all of the data.

Message Edited by Kenny K on 05-22-2007 11:51 AM

[AdnanZ]

Hi Kenny,

There are two methods for moving data from one computer to the other. Is it possible for you to try the second method and let me know what happens.

Across a network: Archive the database to another computer.
1. Open Measurement & Automation Explorer (MAX)
2. Right-Click on the database under Historical Data Viewer
3. Select Archive...
4. In the subsequent wizard you can choose databases and their archived location to any networked computer.

Using a storage device: If you are not going to a network computer
1. Right-click the database and select "Detach/Delete..."
2. Detach the database.
3. Copy the whole database directory located in Program Files>>National Instruments>>LabVIEW 8.x>>'Database'.
4. On the new computer, go to MAX Historical Viewer
5. Right-click on "My Computer,"
6. Select "Create/Attach Database..."
7. Browse and select from the data folder copied from the original comptuer.

[Kenny_K]

Thanks for the reply.

The first method is what I was trying at first, but then i hit the problem i described.

I can do the second method, and have done it before.  THe problem is that the database is still named kkreitzer on the new computer. 

 What I ended up doing was to archive the data to the ss data database on the ssemp computer and then delete the ssemp portion on the ssemp computer, and then rename kkreitzer to ssemp.  Not ideal because i lose a couple hours of data, but much better then losing a couple months worth.