If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
join tables sequencialy
is there a vertical limit?
I believe in a UNION query the error is raised when there are too many fields in the source tables. I don't think it matter how many fields are in the output. Even though the output is combined vertically (by row rather than column) the combined total of the fields in the input tables cannot exceed 255. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com |
#12
|
|||
|
|||
join tables sequencialy
On Wed, 26 Nov 2008 07:45:03 -0800, Yossi evenzur wrote:
is there a vertical limit? No. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com |
#13
|
|||
|
|||
join tables sequencialy
hi,
Yossi evenzur wrote: is there a vertical limit? No, only the the maximum size of 2GB per Access database and the amount of RAM should limit it, but its more then 64k rows... mfG -- stefan -- |
#14
|
|||
|
|||
join tables sequencialy
Already responded to in another newsgroup. Please don't post the same
question to multiple separate groups. Regards Jeff Boyce Microsoft Office/Access MVP "Yossi evenzur" wrote in message ... Hi I have 2 tables, with sea temp per date, how can i join 2 tables one with data from 01/01/2008 until 30/03/2008 and another table with data from 01/03/2008 to 01/11/2008. i don't want to cut the tables and don't want to use SQL, is it possible? |
#15
|
|||
|
|||
join tables sequencialy
Yossi,
Can you step back and tell us exactly what you need? Your request is much like hitting a moving target that reveals a little at a time. This wastes a lot of time and effort. Do you have a field count for us? If you truly have too many fields, the solution might look very different than a solution with a few fields. Also, if the date field isn't unique in the individual tables than you could have two or more records in the same table with the same date. How would you want to handle these duplicates? -- Duane Hookom Microsoft Access MVP "Stefan Hoffmann" wrote: hi, Yossi evenzur wrote: is there a vertical limit? No, only the the maximum size of 2GB per Access database and the amount of RAM should limit it, but its more then 64k rows... mfG -- stefan -- |
#16
|
|||
|
|||
join tables sequencialy
Hi Jeff
I put this as a suggestion since i found my self, trying to consolidate 2 tables or more and resorting to SQL, so i thought it would be a nice addition. the same time i was looking for a solution for NOW. sorry if it caused confusion. "Jeff Boyce" wrote: Already responded to in another newsgroup. Please don't post the same question to multiple separate groups. Regards Jeff Boyce Microsoft Office/Access MVP "Yossi evenzur" wrote in message ... Hi I have 2 tables, with sea temp per date, how can i join 2 tables one with data from 01/01/2008 until 30/03/2008 and another table with data from 01/03/2008 to 01/11/2008. i don't want to cut the tables and don't want to use SQL, is it possible? |
#17
|
|||
|
|||
join tables sequencialy
Hi Duane
here it is: i have 2 tables with the exact field structure and names, 240 fields. one table starts on 03/08/2008 and ends on 25/10/2008 the second table starts on 26/08/2008 and end on 22/11/2008. i need treat these tables as one, meaning, i'd like to have one table that starts on 03/08/2008 and ends on 22/11/2008 with consecutive entries and without multiple identical entries, e.g. not to have double entries for 01/09/2008. I have 6 pairs of these excel sheets and i really want to avoid the cut & paste and without SQL IF POSSIBLE. hope this is more clear :-) "Duane Hookom" wrote: Yossi, Can you step back and tell us exactly what you need? Your request is much like hitting a moving target that reveals a little at a time. This wastes a lot of time and effort. Do you have a field count for us? If you truly have too many fields, the solution might look very different than a solution with a few fields. Also, if the date field isn't unique in the individual tables than you could have two or more records in the same table with the same date. How would you want to handle these duplicates? -- Duane Hookom Microsoft Access MVP "Stefan Hoffmann" wrote: hi, Yossi evenzur wrote: is there a vertical limit? No, only the the maximum size of 2GB per Access database and the amount of RAM should limit it, but its more then 64k rows... mfG -- stefan -- |
#18
|
|||
|
|||
join tables sequencialy
hi Yossi,
Yossi evenzur wrote: here it is: i have 2 tables with the exact field structure and names, 240 fields. This indicates, that your tables are not normalized. Tables with more then 20 fields are rare, tables with more than 200 fields... See http://en.wikipedia.org/wiki/Database_normalization mfG -- stefan -- |
#19
|
|||
|
|||
join tables sequencialy
On Wed, 26 Nov 2008 23:32:01 -0800, Yossi evenzur
wrote: Hi Duane here it is: i have 2 tables with the exact field structure and names, 240 fields. one table starts on 03/08/2008 and ends on 25/10/2008 the second table starts on 26/08/2008 and end on 22/11/2008. i need treat these tables as one, meaning, i'd like to have one table that starts on 03/08/2008 and ends on 22/11/2008 with consecutive entries and without multiple identical entries, e.g. not to have double entries for 01/09/2008. I have 6 pairs of these excel sheets and i really want to avoid the cut & paste and without SQL IF POSSIBLE. hope this is more clear :-) One thing that may not be obvious: there is *nothing* magical about SQL. Don't confuse the language SQL (short for Structured Query Language) with the software product SQL/Server! All queries, whether built using the query grid or not, are SQL; it is *the* language of queries. So you're using SQL any time you use Access. Since you're dealing with non-normalized spreadsheet data, I fear a UNION query will indeed give problems. However it should be possible to create a local table in Access with the same 240 fields; you can set a unique Index on the field or combination of (up to ten) fields which define "a unique entry". You'll then be able to run Append queries to migrate the data from the spreadsheets into this table; duplicates will be removed in the process by this unique index. If there are more than ten fields that define a duplicate you can remove the duplicates later if need be. -- John W. Vinson [MVP] |
|
Thread Tools | |
Display Modes | |
|
|