No this is not a safe approach. This is because other tables have a reference to the data in the notes table.
You would also need to delete the reference to the notes master from these other tables. I think these fields are called Noteidx and Noteid. However it's quite a lot of tables that you would have to check.
The safest way to remove notes is to do so from the entry screens. This removes all references in all linked tables.
It would be possible to do a join between the Customer Master table and the Record Note Master and delete only notes that have a Note Index which exists in the Customer Master table.
David Musgrave
Senior Development Consultant
Asia Pacific Professional Services
well i was just searching for this and found it in this thread so i just gave it a try. hey one more thing have you worked directly with the tables to make it a source of some other database of some other application ? i am into such development at the moment where i might have to make one database as a meta database of all the databases. its getting quite complex for me how to go through it.
I used SQL to something similar integrating our CRM product with Dynamics, Outlook and our plant production system. If you know SQL, things are not that bad. Finding data in Dynamics though often is a pain --- I had to get a shovel and dig to find some things that were not documented too well.
My applications are all triggers, stored procedures, custom views & DTS that I installed onto our Dynamics databases to pull the info one way or the other. I also push things to a reporting db for my intranet reporting.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.