Scott,

I think Edward's idea might be what you need do. It's possible that the driver you're using only supports up to 8 connections (I don't know why it would, but that's what it sounds like). The connection busy message occurs when you try to execute two commands at once over the same connection. To avoid this make sure that your connection is not set for asynchronous execution and that each view has the number of records to fetch at a time set to -1 (all). This will ensure that each view finishes execution before the next one is open.

>Edward,
>
>Thanks for the input but no luck. After I checked the Shared Connection box, I ended up getting "Connection Busy".
>
>We're attempting to try a different driver but we're having difficulty loading it.
>
>Any other ideas?
>
>Thanks,
>
>Scott