Please clarify the BCB5 situation...

Hi

I've been away from these newsgroups for (too) long, busy working on a
non Nexus/BCB product and have now returned to my BCB/Nexus product,
only to find that the situation has changed a little...

Am I right in thinking that changing the Nexus source from 'virtual' to
'dynamic' will fix the problems or are there other gotchas lurking in
the shadows?

As changing one word to another (with the previously mentioned macro) is
no big deal I wonder if there are other things I should be aware of?

I'm glad to see that Nexus will provide support for existing BCB5 users
but I wonder how they can both support us and not produce a working BCB5
version - I would have thought one went with the other?

For me, and for many others, going to BCB6 is just not an option - a
cursory glance of Borland related newsgroups highlights that there are
more issues with BCB6 than I care to mention... True, BCB5 has its
issues, but I now have a working code base in BCB5 and the pain of
trying to get it BCB6 compatible is not appealing, especially as I am
aware that it may not even be possible.

If I can't be sure of a stable Nexus environment for BCB5 I may have to
scrap my current project with some 4 month's worth of work going down
the drain... not an appealing prospect at all. I only changed from
FF1.57 to Nexus because I wanted a supported DB environment. The irony
being that FF1.57 did everything I needed it to...

Currently, because of my other commitments, I am working with Nexus 1.03
and have not noticed anything untoward (yet). Can I assume that the
basic usable of the Server, SQL, Session, Table and SQL components is
OK?
--
Andy