I understand that Access has a 2 gig size limitation. I have over 5 gigs of data to complete a database application. So I have a database file with all pertinent forms, queries, tables, reports, etc. I want to link to database file to this original. These two files will house 1 table each. The information in each of these files will simply house a table that will hold all information that didn't fit into the first table. I understand that you can link an infinite number of database files together. How do you link one database file to another database file and insure that queries running on the front end will process data from the additional database files?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Linking database files.
- Thread starter erwin001
- Start date
I don't have your answer, just an observation. You have 1 table?? Have you thought about Normalizing? Access is a RELATIONAL database, not a container to dump data. You must have quite a bit of redundant data.
5 gigs? That reminds me of my days at the old AT&T. Have you thought about any database made for a mainframe like IMS? Even Social Security Administration, that also has 5 gigs of data, uses mainframes.
Something doen't feel right.
5 gigs? That reminds me of my days at the old AT&T. Have you thought about any database made for a mainframe like IMS? Even Social Security Administration, that also has 5 gigs of data, uses mainframes.
Something doen't feel right.
... you can link an infinite number of database files together
Not exactly. You don't link tables together. You do link different tables to a database. I know of no mechanism for creating true distributed tables (i.e. tables that are treated as one logical table but have parts of the table in physically distinct locations) in Access. You can link your separate tables into a single database but they remain distinct tables and things like unique keys or relationships will not be enforced among those distinct tables.
And fneily is right ... 5GB is a massive amount of data. It may not require a mainframe to handle it but Access is not a client-server DBMS and, if you're running on a network, you will be moving all that data over the network. Performance will probably be in the "... sometime next week ..." range.
[small]No! No! You're not thinking ... you're only being logical.
- Neils Bohr[/small]
Not exactly. You don't link tables together. You do link different tables to a database. I know of no mechanism for creating true distributed tables (i.e. tables that are treated as one logical table but have parts of the table in physically distinct locations) in Access. You can link your separate tables into a single database but they remain distinct tables and things like unique keys or relationships will not be enforced among those distinct tables.
And fneily is right ... 5GB is a massive amount of data. It may not require a mainframe to handle it but Access is not a client-server DBMS and, if you're running on a network, you will be moving all that data over the network. Performance will probably be in the "... sometime next week ..." range.
[small]No! No! You're not thinking ... you're only being logical.
- Neils Bohr[/small]
- Thread starter
- #4
Anybody that "will not allow me to store just the link to the OLE object" can afford to buy, install, and maintain SQL Server.
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
- Thread starter
- #6
Individual users would only need to be licensed to access the sql server. You can use ODBC or other methods to connect to tables on the server.
If you don't have any experience with SQL Server, I don't recommend learning while working for a client.
You might want to consider Stephen Leban's solution at
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
If you don't have any experience with SQL Server, I don't recommend learning while working for a client.
You might want to consider Stephen Leban's solution at
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
- Thread starter
- #8
- Thread starter
- #9
What would be some get arguments to present to the customer regarding embedding OLE objects within a table, as opposed of creating a link. In my application, I have a two tab form. Report attributes are contained in tab 1, the OLE object is shown in tab2. Is it possible to create a link to a folder holding the OLE objects, so that when tab 2 is clicked the entire object will cover the tab?
Check this link on Displaying photos in a form.
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
- Thread starter
- #11
- Status
Similar threads
- Locked
- Question
- Locked
- Question