Re: Importing .XLS

On 4 Ott, 23:51, Joel <johow..._at_gmail.com> wrote:
> > Anyway they can be easily renamed.
>
> Easily?!? I'm the one that faces hundreds of tables (data collection
> projects) that commonly have >20 columns! You do the math... Not only
> that, but there is a limitation on the maximum field name length.
> Correct me if i'm wrong, but I believe the name can't be longer than
> 30 chars. I really don't like having to go back to determine which
> field name is causing my create table statement to error out.
>
> > The following procedure is **only** to determine such maxima. Then,
> > you can use
> > these value to substitute the default values in "Table setup" for the
> > export to DBMS:
>
> I want a tool that will do that for me.
>
> Seriously, what century are we living in? Maybe I should be asking if
> anyone has the appropriate punch cards...

 :-)))

It wouldn' really cost me much to add the functionality you are suggesting (automatically passing the maxima to the create create statement), but I am a little bit lacking conviction currently, and I feel I need some more arguments to get persuaded about the usefulness of such an automatism.

Usually the field sizes should be based on some design planning and not just because you found string of some lenght in an Excel sheet. Not to mention the encoding issues.

And what about someone add a char to string. Are you going to recreate your table ?

[Quoted] Sometimes (it may not be your case), when one feel there is a lack of tools, it may also be worth considering to take this as an hint to think about the approach being used.

Cheers,

-P Received on Fri Oct 05 2007 - 00:20:47 CEST