has anyone else come across problems importing tables with blank date fields (which are correct) on SQL7/NT/Baan5c ??

I would not mind knowing what exactly the problem is? What kind of errors are you getting?

This sounds like a problem that appears in 4c4 with service pack 6. This is only occurs with MS SQL 7 and creates so many problems.. There is a patch and a correcting program for 4c4, but I havn't come across the Baan5 solution.

We run Ora805/HPUX/4c4 and also have the same problem.

Ravenscross you mention that there is a patch and corrective program for this. Do you know the soluton number by any chance. I've searched the Baan KB, for what it's worth, and found nothing. (Surprise, Surpirse)

Thanks

P.S. We are on SP5

It seems like the change company number session corrupted some of the dump files. Need to make a new dump of the live company which will have to wait until the weekend.

Then we can try it again and report back

Cheers

Andy
andy@baanassist.com

Not sure about the solution number, but if you search on the BaanKB for 'Error 205' (I think), you should find the file. Of course, this is all coming from memory (I really should write this stuff down)

We had a similar problem when migrating data from Oracle7 to SQL2K.

We had some 'duff' dates in a couple of tables that Oracle didn't care about but SQL saw that they were out of sync (i.e. 1345 AD etc). At this point the sequential dump 'skipped' this table and so were left with incomplete data.

The only way to fix this was to either edit the data manually or write an exchange script to modify/migrate the data.

After much torture and reading of much awful documentation, I have managed to upgrade to Baan5c Service Pack 6, latest portingset, plus latest SQL service pack (nice >40Mb download!)

The problem seems to have been rectified somewhere along the way.

There was a brief moment of panic when we couldn't get into (amongst other sessions) Maintain Purchase Orders - but this was fixed with yet another tools patch!

Andy :)