Import data - problems

Ruslan Zasukhin ruslan_zasukhin at valentina-db.com
Tue Aug 25 00:28:01 CDT 2009


On 8/25/09 4:00 AM, "Barry G. Sumpter" <barrysum at bigpond.net.au> wrote:

Hi Greg,
Hi Barry,

My advice will be next:

Make in Vstudio TABLE wit fields as you want.

Fill 3-5 records.
EXPORT to text file using EXPORT Dialog.

Now you can see what format of text file expect Valentina engine on input.

Of course it can sometimes import even little other format.
We did spend time in the past to be able import correct format from Access,
Excell, mySQL and others.

Yes, most sensitive things are DATE, TIME,


2) Do you mean that Vstudio crashes on import?
   this should not happens. If yes, I will ask you
   report this to mantis with db + text file.

> One of the responses here was to just make everything text fields.
> Then run update queries to fix.
> 
> With deductive reasoning:
> Just import one record.
> Errors.
> Just import half the fields until you identify which field.
> Fix that field and any others like it.
> Go from there.
> Etc
> 
> Date formats are wrong.
> Numeric fields are wrong.
> Etc.
> 
> 
> Using Valentina Studio Pro
> Create a new table yourself with the datatypes.
> Enter data by hand.
> View the data and see the format.
> 
> 
> 
> The latest n greatest is Valentina Studio Pro 4.2
> which I believe Paradigma is offering a free license to the end of the year.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list