Thanks Gilbert and Christof for the quick replies.

Gilbert,
Thanks a lot, changing the varchar to char worked. 
But any idea why???
And why is it that the other tables (which all have varchar columns) can 
be opened OK, but not this one?????


Christof,
Thanks. 
We changed the Number(11) and Float(126) to a Number. Sounds obvious now 
that you mention it. 
No astrophysics involved by the way- the reason for the Float(126) was 
that this was the default when the long integer was brought in from 
Access!

Thanks again,
Steve

______________________________________________
Gilbert Hache wrote:

I beleve I saw this one before a while ago... change varchar format to
standard text. Easy enough to test isn't it?
______________________________________________

Christof Kaiser wrote:

I would try to change the Number(11) and Float(126) to a Number. (default 
is about 22 I think).

What the hell do you need a float(126) for?
That seems a bit over the top unless you are doing serious astro-physics.

The number(11) might cause problems as it doesnt fit into a 32 bit MapInfo 

Integer.
So try NUMBER without an argument (which has, in fact, a bigger range but 
MI doesnt care about that.)

please let me know how you go.
______________________________________________

 
___________________________
Steven Kalma 
Integrated Data Solutions
URS Netherlands B.V.
 
+31-(0)70-336-9089 (direct)
+31-(0)70-319-2112 (switch)
+31-(0)6-5342-8976 (mobile)
+31-(0)70-319-1125 (fax)
 
[EMAIL PROTECTED]
www.urscorp.com/europe
___________________________
 

Reply via email to