Hi Jemacc,

I have mailed you the executable that splits the table in to required size(in terms of number of rows).

Cheers!

_________________________
-Vijay G
Strive for Perfection

I will try it and get back to you with results. Thank you for your time and effort.

I tried the executable but with no success. can you layout and example of how is to be executed.

Here is the error message. "NTVDM HAS ENCOUNTERED AN ILLEGAL INSTRUCTION CS:0000 1P:007 OP:F) 32 05 12 02"

close or Ignore

I am reluctant to run it again because I do not know what it consist of or what it is touching on my system.

Thank you

It is just a VB Application that I wrote based on the table structure that you posted here.

It worked fine, I tried with some huge amount of data in there and worked as expected. I also tried runnin git from different system from which I originally developed that, and found no errors.

Just puzzled



_________________________
-Vijay G
Strive for Perfection

This is the format I used to execute your VB executable

splittable.exe ServerName, Database Name, UserId and Password, Source Table Name, xxxxxx

How did you execute it?

May be my explanation was insufficient.

You can double click that Exe as it would popup a window where it asks for Servername, DBName, Uid, Password and required other info, then Press "SPLIT TABLE" button there, it would popup a message "Tables Split Completed", then you can check you DB for tables with suffix, 1-X (TABLENAME1, TABLENAME2...) with the number records in it, that you provided at the time of execution.

Let me know if any issues.

Hope that helps.
Cheers!

_________________________
-Vijay G
Strive for Perfection

I have tried from Windows xp machine, windows 2000 advanced server and I still received the same error.

Is ther something specific I should be doing.

use a simple SQL statement
SELECT * INTO table1 FROM yourTable
WHERE ID > startRange AND ID <= endRange

I think the syntax for Access is
SELECT * FROM yourTable INTO table1
WHERE ID > startRange AND ID <= endRange

Vijay G

I will like to thank you for the time you have taken for this and do I appreciate everything. This just did not work for me and I had to go about it the long way. I will try when I have more time.

I guess by now you are into the process of splitting your table into multiple tables. I am pickin back where Jeff Mason mentions multiple tables. Your table structure may be fine and all you need is some additional look up table to group your records.

When a comapany has employees, hte comapny does not create sepparate tables for managers, another for blue collars and another for others. By breaking up your table you will at some point have to join this tables by either joins or union statements. When that day comes, your database will crash because of the slow process of joining tables on some criteria.

Try looking into your indexes first and if this is just coordinates, keep just coordinate information in the table with the proper datatypes.

Coordinates do not ussually change either, consider MSDE for this data instead. The number of records may not be for access whether you split your database or not, but you will not know that unless you first try to look at your indexes first.

29 mil records plit into so many tables will crash for sure. If you break up your table and your indexing is wrong, do not place the file in the network as this will not only kill your access database, but it will kill your network because of the traffic that this will create.



Sal