Thanks for your reply Ashwani.  Perhaps it's because I am in V4.0, 
but there is no opportunity to specify "drop" anywhere - the 
synchronise starts and fails.  I have tried turning the config key 
back on (synchrnise is ok) and the off again (same error).  Finally I 
have added the column to the table manually and then synchronised ok 
to remove it.  All is now ok.

Hans

--- In [EMAIL PROTECTED], ASHWANI JAIN 
<[EMAIL PROTECTED]> wrote:
>
> Hello Hans,
> 
> AOT contains all the object, even if the license if not there or 
the configuration key is removed for the corresponding object. On the 
basis of this license + configuration key, when we synchorize the 
application with database, system (application) checks which fields / 
tables are applicable and then creates only those object in the SQL 
server table.
> 
> As you mentioned that you are not able to delete the field, which 
is there in AOT. This is correct. Any field which has ben introduced 
in lower layer can not be deleted in upper layer. 
> If MS allows this, then user will delete the functionality provided 
in Ax, and later on not able to recover and I think this is the good 
functionality provided in Ax. to control based on Layers.
> 
> During synchronization, when system ask you to drop the fields / 
table, you should have to select the DROP option for the fields / 
tables system asks. I am sure once you execute this, you will not 
encounter the problem.
> 
> Any further query is most welcome.
> Regards,
> Ashwani Jain
> 
> 
> ----- Original Message ----
> From: hkruiniger <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Wednesday, 4 April, 2007 8:53:02 PM
> Subject: [Axapta-Knowledge-Village] Synchronise error - drop non-
existent field
> 
> Problem: table definition in AOT specifies a field for which there 
is 
> no column in the actual SQL Server table. I have turned off the 
> config key responsible for this field and now synchronise wants to 
> remove it from the table, but gives an error since the column is 
not 
> there to be dropped! I can't remove it from the table definition in 
> the AOT - clicking on "Delete" appears to have no effect at all.
> 
> I suppose I could manually add the column to the table, just so 
that 
> synchronise can remove it, but that seems silly.
> 
> Any ideas?
> 
> (details FWIW: table is EmplTable, field is ActivateAnswer, 
switched 
> on/off by smmPhone config key)
> 
> Hans
> 
> 
> 
> 
> 
>               
> __________________________________________________________
> Yahoo! India Answers: Share what you know. Learn something new
> http://in.answers.yahoo.com/
> 
> [Non-text portions of this message have been removed]
>


Reply via email to