Microvellum Knowledge Network

Is it ok to copy cells and/or formulas between MV databases, particularly if one is on a newer release?

We split our database a while back to make a "clean break", and we have old jobs in one database, on an older update (15.6), and new jobs in another database, on a newer update (from 22.1).  Occasionally, people want to copy cells, formulas, etc. from the older one into the new, to save on engineering time.  MV seems to be very finicky when it comes to this.   Sometimes, some of the copied stuff disappears when they close out and re-open.  Other times, not everything actually transfers when pasting in the new workbooks, only certain cells. 

So, I was wondering if this was generally considered an acceptable practice, or if it could potentially cause jobs to become corrupt or have background errors.  Obviously, the logic could get messed up, if the copy/pasting goes awry, but even if it appears to work fine, could be it causing other issues that may be less obvious?  For example - one of these jobs with copied logic is now incredibly slow to open, redraw, etc. (but that could definitely be unrelated).

Copy/pasting can speed us up on some of our jobs, but it is making me a bit nervous with how unpredictable it is between databases/releases...

    MVU eLearning



    Grow Your Knowledge
    Follow along with RJ as he takes you on a journey to build your foundational knowledge of Toolbox.


      Follow us on:

               

        Google Review