Hey All!
Our organization recently had a meeting in which we determined that half of us are entering and tracking individuals in MS Access (Artistic, Education, and Production), while the other half is working in Tessitura (Marketing, Development, and Box Office). As you all know, we're more often than not trying to enter and track the same individuals, and the two halves of the organization often have a heckuva time keeping one another posted across the separate tracking systems (Stop me if you've heard this one before!) ... and of course, each has been building their own database that sometimes agrees with the other, sometimes not ...
So for the moment, the nature of the processes in place and some of the data entered dictates that we're going to live in this sort of yin and yang world. As such, I'm wondering if anyone has found a successful way to import data from Access into Tessitura (forgive me if this feature is built-in ... I'm kind of a noob)? Can such an import be used to create new constituent records or modify existing records? I presume if it's possible that there will be certain pitfalls or caveats to watch out for ... ?
Any guidance that anyone has to offer in this regard is much appreciated! Forgive me if this is already posted somewhere, I attempted to ferret it out but came up dry ...
Thank you!
Brian Jones
Unknown said: [...] I'm wondering if anyone has found a successful way to import data from Access into Tessitura (forgive me if this feature is built-in ... I'm kind of a noob)? Can such an import be used to create new constituent records or modify existing records? I presume if it's possible that there will be certain pitfalls or caveats to watch out for ... ?
[...] I'm wondering if anyone has found a successful way to import data from Access into Tessitura (forgive me if this feature is built-in ... I'm kind of a noob)? Can such an import be used to create new constituent records or modify existing records? I presume if it's possible that there will be certain pitfalls or caveats to watch out for ... ?
I've done Access -> Tessitura imports here a number of times. I'd second everything Levi said above: the attribute he mentions (with which you can join Access records to Tessitura records) is especially key.