Question: I have multiple ~50MB Access 2000-2003 databases (MDB files) that only contain tables with data. The *data-databases* are located on a server in my enterprise that can take ~1-2 second to respond (and about 10 seconds to actually open the 50 MDB file manually while browsing in the file explorer). I have other databases that only contain forms. Most of those *forms-database* (still MDB files) are actually copied from the server to the client (after some testing, the execution looks smoother) before execution with a batch file. Most of those *forms-databases* use table-links to fetch the data from the *data-databases*. 

Now, my question is: is there any advantage/disadvantage to merge all *data-databases* from my ~50MB databases to make one big database (let's say 500MB)? Will it be slower? It would actually help to clean up my code if I wouln't have to connect to all those different databases and I don't think 500MB is a lot, but I don't pretend to be really used to Access by any mean and that's why I'm asking. If Access needs to read the whole MDB file to get the data from a specific table, then it would be slower. It wouldn't be really that surprising from Microsoft, but I've been pleased so far with MS Access database performances. 

There will never be more than ~50 people connected to the database at the same time (most likely, this number won't in fact be more than 10, but I prefer being a little bit conservative here just to be sure).

Answer: 
Something like this?

```
var points = File.ReadLines("c:\filepath")
    .Skip(1) //Ignore the 1st line
    .Select(line => line.Split(' ')) //Chop the string into x & y
    .Select(split => new Point(double.Parse(split[0]), double.Parse(split[1])); //create a point from the array

```
```
var coordinates = File.ReadLines(fileName).Skip(1)
                    .Select(line => line.Split())
                    .Select(x=>new PointF(float.Parse(x[0]),float.Parse(x[1])))
                    .ToList();

```