[coimbre 21]

Oh, ok. I didn't explain myself very well. What I meant by my comment was that there may be issues that we don't see that need to be done that take priority over the registry. There may be issues that need to be taken care of in order for the registry to even function. That's what I meant.

Sorry for the misunderstanding that I've caused.

You're OK man and as you know my very high level of registry frustration is well documented. You are correct though, IT Guy explained in one of the threads that development of the new registry is the holdup, not really the migration of the database. The old registry is also sitting on their old storage and server platform that apparently has been decommissioned so that's why the old one is gone. Apologies if it sounded like I was hitting you with hard sarcasm.

---

they can take 5 mins and tell us SOMETHING.

"Hi valued customers, we want to get the registry going but we've got other problems and foresee a summer 2012 timeline for registry"

They could hire ONE geeky database guy and have a BRAND NEW registry launched in a few months and then pay a high school kid $10/hr to key punch the legacy data into the new system and be done faster than this. This is pathetic.

That's all we've been asking for . . . one sentence with an update.