I expect that the AOT would complain the complete set of fields on a table. If you have used configuration keys to turn off features that would introduce fields, these fields would already be in the AOT (it must in order to compile clean) but not in SQL. Turn on the configurations and Axapta will Synchronise and create the columns it needs to.
Steve. -----Original Message----- From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Peter CCH Sent: Wednesday, 19 October 2005 2:35 PM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Axapta Data Dictionary and physical table tructure not match I open the table structure in Axapta Data Dictionary and physically open the table structure of the database. I found that there's some slight difference between it. I can see about 13 fields extra at the table in Axapta Data Dictionary, but when I physically look at it the physical database structure (Oracle), that 13 fields is not in there. I tried synchronize the data dictionary and even particularly synchronize that table, but it still the same. Is there any possibility that a license will restrict the field creation in physical database? Or how this could happen? ---------------------------------------------------------------------- ---------------- I started to look at it when there's some error logged into SysTraceTableSQL. Peter CCH Sharing the knowledge on Axapta. Yahoo! Groups Links ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/kGEolB/TM --------------------------------------------------------------------~-> Sharing the knowledge on Axapta. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Axapta-Knowledge-Village/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
