MMC is crashing nearly all the time when I exit the Package Designer on
SQL Server 2000 with SP4. Now most of the create table icons don't
show but they run. Could this crash be because I have 400+ tables
covering 10K plus fields and so I just pushed this Microsoft Package
Designer over the top? I initially created the package from the
package wizard. I can't find any fix to this MMC crash. The machine
has 3GB of RAM, loads of disk space, and is otherwise running great.

A related question to this is that the project involves migrating about
5GB of Informix data to SQL Server. I don't need any fancy data
conversions. I have all the constraints, indexes, views, functions,
procedures, and triggers separately converted to SQL Server syntax
already and they are loading fine when run from Query Analyzer. I was
hoping I could just copy all the calls into Execute SQL Tasks. BTW, I
tried saving the package as a VB file but it is about 250K lines long!
It cashes VB6 but I can load it in Visual Studio 2003 but the
conversion to VB.Net was not progressing well so I went back to the
Designer.

Am I just using the wrong technique or technology entirely for this
migration project? Should I try to get this all working with VB 6 or
VB .Net?

I never got a reply and gave up on MMC and using precreated packages.
I have decided that I was just doing it all wrong. May be I'm still
all wrong. My next completely different approach is to write code to
the DTS SQL 2K objects in VB6. I'm now stuck on two things, identity
inserts and not doing any transforms just fast bulk copies from
Informix to SQL Server without coding each field of a zillion tables as
the wizard output did in the 250K line 8MB BAS file export. If you
have any thoughs on this monstrosity, I'm all ears. Otherwise, I'll
start new treads as need be.