Swap Database?
Altair EmployeeI have two exact databases, one is month end (me1), one is previous day (st1). I wrote a pretty elaborate report on the month end database and now I'm being asked to provide it mid-month as well so I want to switch from the me1 db to the st1 version. Same tables, same fields. Is that even possible? I can't find a spot anwhere that allows me to change the source. It doesn't look like I have change path options like when I use PDFs or spreadsheets. When I try going back to start page it adds in the whole second database, or if I start with the st1 database and then try and open the report workspace, it wants me to close my existing workspace.
BLARGH. Really hoping I don't have to rewrite the whole report... Any ideas?
Answers
-
Sounds like you are using Data Prep Studio. If you open your workspace and look at the Prep Data tab, you should see your table that is loaded on the left side. If you left click the drop down arrow, you will see several options. The one you are looking for is "Edit File Path"
Select it and browse to the new database that you want to point to.
0 -
Altair Forum User said:
Sounds like you are using Data Prep Studio. If you open your workspace and look at the Prep Data tab, you should see your table that is loaded on the left side. If you left click the drop down arrow, you will see several options. The one you are looking for is "Edit File Path"
Select it and browse to the new database that you want to point to.
Tried that. Left click does not bring me to "edit file path" when I'm using an OBDC connection.
0 -
Ok. Just want to throw out the obvious one to reconfigure the ODBC entry, but I am going to guess you have other tables or workspaces that use the same entry so that probably won't work. The second one would be to start a new workspace, but export the existing change list from the current one and then import it in the new workspace.
0 -
Altair Forum User said:
Ok. Just want to throw out the obvious one to reconfigure the ODBC entry, but I am going to guess you have other tables or workspaces that use the same entry so that probably won't work. The second one would be to start a new workspace, but export the existing change list from the current one and then import it in the new workspace.
Ooh... I like the idea of exporting the change list. Hadn't thought of that and will try that next. Thanks Chris!!
0
