|
Posted by Mickie on November 3, 2008, 12:50 pm
Please log in for more thread options I agree.
A separate table with the ILC and ASIN as the 2 fields would work for you.
You could query out your combined table and import it into Amazon's item
lister program.
convoluted wrote:
> Thanks for posting a reply Antonio - having said that, would it make more
> sense to create a separate table then join it to the item table ( kind of
> like the alias table), since the only purpose is to access the ASIN via
> queries? May need to consider also that future versions of the software may
> have an issue with that added column. Thanks again for sharing your knowledge
>
> "antonio" wrote:
>
>> On Oct 30, 6:37 am, tfi...@gmail.com wrote:
>>> Are there any incompatibility issues I would need to worry about in
>>> adding additional columns to tables in the database? I'm already
>>> using most of the available fields in the item table and I would like
>>> a place to store each items ASIN assigned from amazon. I don't need
>>> to be able to read or write this in either the POS or the Manager, I
>>> just need to be able to access it through SQL queries.
>>
>> you can add a custom columns in Item table with this statement
>>
>> ALTER TABLE [Item]
>> ADD [ColumnName] NVARCHAR([size]) DEFAULT('') NOT NULL
>>
>> it's important a DEFAULT value, otherwise the Manager and the HQ
>> Client can't create new items on database....
>> in addition, you must add the field on offline databases and hq
>> databases (or viceversa) because the sync. procedures
>> get all fields
>>
>> antonio
>>
|