Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
How do I interpret the following result ("Purchases-1"), when trying to create a unique key, and return it within the "Purchases" table?
This only happens, in my much larger file - and not in the small qv file I created for troubleshooting/testing (where the "Unique" field is being returned in the "Purchases" table, and "Purchases-1" is not visible).
Only difference between the two docs, is that the original has a lot more data/fields/tables.
This table appears ("Purchases-1"), when my script fails to load, following the attempt to create the unique key ("out of virtual memory" error). Knowing that my syntax appears to be correct, ie it works in the attached test file, Im puzzled as to why I am experiancing issues in my larger file - or is it just that, my file is too big for my machine?
Anyone have any ideas/suggestions?
Kind regards,
Rich
Hello Rich,
That table naming usually happens when a table named alike already exists, and it may happen because of a table with the same structure read later and the first not dropped. Since it appears as one table with only one field, is there any chance that you are loading using DISTINCT or MAPPING or something the "Unique" field, and only this field?
When does your script fail?
Hope that helps.
Hello Rich,
Taking a closer look to your code, the issue is that you are loading (2) from an already loaded (1) table, then joining (3) with the first table. If you are doing this because you want to create the Unique field, do the following in the excel load:
MaterialFamilyMap:MAPPING LOAD MatDescID, FamilyFROM UniqueField.xls (biff, embedded labels, table is Materials$); Purchases:LOAD MatDescID, SupplierID, CalYearMonth, Euros, QtyG, ApplyMap('MaterialFamilyMap', MatDescID, 'No match') & '|' & SupplierID AS Unique FROM UniqueField.xls (biff, embedded labels, table is Purchases$);Hope that helps.