Saving Tess files w RAMP

Re-posting in case someone out there has answers!!

-----

Hi all,

We are on RAMP and the various paths to save files from Tess are arduous. Is there a way for users to indicate a default location for files to be saved? Currently it's a very nested path of folders that is compounded by slow response.

Thanks,
Megan

Hi Megan,

We are also a RAMP site and have the same problem. I've noticed that once a report has been saved to a particular location on our internal network, future runs of the same report will default to the same location. Which makes life a little bit easier, but not for first time runs.

I don't think there is any way around this as the RAMP server initially sees its own network and only sees your network once it's been taught that it exists. The slowness is probably due to the data coming over your external connection. We've recently had our external connection upgraded and saving reports is better - not perfect, but better.

Hopefully someone else will offer more useful comments!

Debbie

We have had similar experiences, so I have a tip I have found useful and have shared with our staff, who seem to use it when they need to. 

I have a folder on our main network drive (not the local RAMP network, but OUR network drive) and it's a folder I've named .RampFiles (notice the '.' at the beginning, which will then sort that folder to be the first to appear when you go to save a file from Tess after you access your network drive).  It helps because then you don't have to sort through a thousand folders through the RAMP connection and cuts down on the wait time. 

After you save to the folder, you can go back in through your network and save it again to where it needs to actually go and delete the original file if you need to. 

It's tedious at first, but I"m so used to it by now, I'm able to save quickly with no problems.  :)  I hope this helps. :)

We have had similar experiences, so I have a tip I have found useful and have shared with our staff, who seem to use it when they need to. 

I have a folder on our main network drive (not the local RAMP network, but OUR network drive) and it's a folder I've named .RampFiles (notice the '.' at the beginning, which will then sort that folder to be the first to appear when you go to save a file from Tess after you access your network drive).  It helps because then you don't have to sort through a thousand folders through the RAMP connection and cuts down on the wait time. 

After you save to the folder, you can go back in through your network and save it again to where it needs to actually go and delete the original file if you need to. 

It's tedious at first, but I"m so used to it by now, I'm able to save quickly with no problems.  :)  I hope this helps. :)

Tiffany, on first attempt it seems to already be a big help. Thank you!!

Debbie, I tried to post a response to you but I think I failed. But here it is-

Normal 0 false false false EN-US X-NONE X-NONE Thanks for your message. I want to clarify - after you've saved a report on your network, future saves default to the same location, even days later?

That is not the case on our system. Sometimes I have that within a session of being logged in, and sometimes the memory is wiped even within one session. Same story with importing lists, though the time window there is much shorter.

Megan Hall
Seattle Symphony