Peter J. Boettcher — Wed, 20 Mar 2002 16:22:52 +0000

Before you spend too much time with your ASP script I would test importing data into SQL Server using Enterprise Manager. It's not guaranteed to work but it is more robust and flexible than the import wizard in Access.

akohl — Wed, 20 Mar 2002 15:47:14 +0000

Well, it seems that I'll be getting sql server soon.
So I'm going to leave the problem with the access import wizzard unsolved.
The question now is, should I continue to work on the data import asp script that I started this thread with? Once I get the simple version above to work, I'm going to develop it further so that it will be able to use it to import from one text file into two tables, since some of the data in the file belongs to another table in my db.

Will I be able to do all this with the db program itself and am I therefore wasting my time with this script?

Peter J. Boettcher — Mon, 18 Mar 2002 14:05:21 +0000

You don't have to have SQL Server installed on your machine. If your webhost provides a public IP on the SQL Server machine you can use it for development. So on your development machine the connection would point to the SQL Server.

Once the database has been created you can use Enterprise Manager to manage it.

akohl — Mon, 18 Mar 2002 11:40:10 +0000

Is it possible to use ms sql server on the webhosting server without having it installed on my own computer? Would would a webhost be able or willing to convert my access db to ms sql server so that I could do all the development on my own computer with access but have the website run on sql server?

Peter J. Boettcher — Fri, 15 Mar 2002 17:44:15 +0000

You shouldn't have to modify anything except your connection string, but you'll probably want to convert all those queries to stored procedures for efficiency.

There might be some minor problems since SQL handles it's datatype a little different, but they should be minimal.

akohl — Fri, 15 Mar 2002 14:06:12 +0000

The file is 1.1 mb

No I don't have ms sql server. But I have a feeling that I'll be going in that direction eventually. I didn't think I would have to do so even before the project goes on line.

Tell me- If I continue to devlope the site with access will it be easy to convert it to sql server later? Will I have to change the sql on my asp pages?

Andy

Peter J. Boettcher — Thu, 14 Mar 2002 13:34:15 +0000

That's the problem with Access, it has many limitations. I think you might be able to get around the 64K by importing through your ASP page but I'm not sure. I'm not sure what the limit is on how many memo fields you can have in a table but I would think each one would have the same 64K limit.

How big is this text file? Access has actual file size limits, something like 1GB or 2GB.

If you have access to a SQL Server then maybe you should try importing the text file there using the tools built into Enterprise Manager. Then maybe it will be easier to export it from there to Access.

akohl — Thu, 14 Mar 2002 03:35:16 +0000

I tried again. It said that i had a line of data with over 65,000 characters. Its hard to believe, but possible I suppose. Will I have the same problem when I try to import the data with my asp script?

Curiously, it didn't say that one field was too big to fit into a memo field, It said that the line was too big. I previoulsly understood that I could have three memo fields of 30,000 characters each in the same table. So what gives here?

akohl — Thu, 14 Mar 2002 02:36:02 +0000

I wasn't aware of the import wizzard.

I just took a look now but had trouble with it. It couldn't seem to work out how the fields were deliminated. So I clicked "advanced" in order to tell it that the fields were deliminated with spaces and strings were qualified with double quotes. The access crashed out and said I had one or more fields in that data source that was too big to import.
When working properly would that wizzard give me controll over the proccess so that I could skip certain fields that I don't want to import, ect..?

Thanks for your suggestion. I hope I can get it to work.
As far as my script is concerned I guess your saying that I just have to review all 20 some db field assignments carefully and that this is the only way to find out which one is causing the trouble, right?

Andy

Peter J. Boettcher — Wed, 13 Mar 2002 21:16:07 +0000

A type mismatch usually means you're doing something wrong with data, either doing calculations on strings, trying to save a string into an integer, stuff like that.

If you want to see where you're going wrong just add a Response.Write strMid or something. If you're strictly just trying to import the data why don't you use the import wizard in Access?