Wouter, I did open it up in MSWord and found that there were no commands in the file, just data.
What makes this worse is that each field is preceded with a tab and a character which identifies the field. Empty fields are omitted to the extent that although the fields run in the sequence A-Z and then a-z, the data shows gaps with no fields and no tabs. So a record might look like this: [tab]ABloggs, J[tab]BTitle of work[tab]F0123456789 and so on. The file obviously relates to a single table and weighs in at a mighty 98Mb. >From what I can see I am going to have to write some sort of parser in PHP or similar in order to get the data into a decent format to work with before its ready for MySQL. If anyone's had to do anything like this before I would welcome any code, comments, help etc. Regards George ----- Original Message ----- From: "Wouter van Vliet" <[EMAIL PROTECTED]> To: "George Pitcher" <[EMAIL PROTECTED]> Sent: Friday, July 12, 2002 7:43 PM Subject: RE: using a '*.seq' file > Hmm, i'm not that much into Oracle but I know that between most Database > Systems small differences are there in the SQL syntax. What I would advice > you to do is just try to run the .seq file (with a ./database.seq like > command) and see what errors it returns. You can then try to eliminate the > problem. > > Most problems will occur with datatypes I guess. Maybe check out some > auto_increment issues ... if you're getting errors out of the .seq file with > whom you don't know what to do, just mail the list. > > Note that an *.sql file is no more than a file containing raw SQL commands > to be executed upon a database. You may as well call it *.MichaelJackson or > whatever. ;). So yes, in basic the files seem to be the same. Or at least I > hope so .. maybe try to open the file in some texteditor and see what it > looks like. > > Greetz, > Wouter > > > ---------- > Alle door mij verzonden email is careware. Dit houdt in dat het alleen > herlezen en bewaard mag worden als je goed omgaat met al het leven op aarde > en daar buiten. Als je het hier niet mee eens bent dien je mijn mailtje > binnen 24 uur terug te sturen, met opgaaf van reden van onenigheid. > > All email sent by me is careware. This means that it can only be reread and > kept if you are good for all the life here on earth and beyond. If you don't > agree to these terms, you should return this email in no more than 24 hours > stating the reason of disagreement. > > > -----Oorspronkelijk bericht----- > Van: George Pitcher [mailto:[EMAIL PROTECTED]] > Verzonden: donderdag 11 juli 2002 13:28 > Aan: [EMAIL PROTECTED] > Onderwerp: using a '*.seq' file > > > I've been handed a 'data.seq' file containing a really useful database. > > This is currently hosted on my future employer's site using Oracle. I wish > to look up some of the data there and pull it into my Filemaker database. > I'm using Filemaker for historical reasons and plan to move to MySQL in a > few months. > > What I want to do right now is see how valid the data will be and what I can > do to access the data is a useul way, so I thought I would put it into MySQL > and then try out Filemaker's ODBC tools. > > Is there an easy way to load the .seq file? Is a .seq file the same as a > .sql file? > > Regards > > George in Edinburgh (but just for another 3 weeks) > > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
