Wine Database getting out of hand!

[Guest]

Hi,

I have built a database with details of all the wines we supply in one
place. I have one table with the text information, one for bottleshots (all
jpg's stored in both HI and LOW res) and some other information.

I have a switchboard which appear when you enter the database allowing users
to navigate the information without every having to deal with the tables. I
have now reached my 2GB limit. My problem is that i have plenty more
information to go in the database and I also need to move the database to our
SQL server.
I have tried upsizing teh database, splitting it and repairing and
compacting it. All these do is crash the machine.

Does anyone have a workable solution?
All help greatly accepted.

 

[Rick B]

As posted many many times in these newsgroups, DON'T STORE PHOTOS IN A
TABLE. Instead, store a link to the photos. Access storing photos causes
severe bloat.

Either store the link to the photos, or break your database into more than
one database file and used linked tables.

Do a search and read the previous posts if you need more details on this.

 

[Guest]

I did read those posts, i just thought i would check if criteria could have a
different solution.