Troubleshooting NEOSYS Media System: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
In most files other files, NEOSYS only stores the main codes like brand code and vehicle code and every time a report needs the client or supplier code it looks up that information from the separate brand or vehicle file so it always gets the latest info. This is how databases usually work. Actually some people would like the reports based on the ORIGINAL codes rather than the latest codes. | In most files other files, NEOSYS only stores the main codes like brand code and vehicle code and every time a report needs the client or supplier code it looks up that information from the separate brand or vehicle file so it always gets the latest info. This is how databases usually work. Actually some people would like the reports based on the ORIGINAL codes rather than the latest codes. | ||
[[Fixing wrong exchange rates in invoices]] | [[Fixing wrong exchange rates in invoices]] | ||
Revision as of 20:59, 4 April 2007
Client / Brand change does not reflect in Media Diary
Unusually for NEOSYS, in the ADS file (on which the media diary and all "List of Ads" type reports and files are based) lots of referential information (like client/supplier etc) is frozen at the point of the last update. Running CREATEADS rebuilds the ads file and therefore gets/stores the latest client, supplier etc info into the ad records. Moving brands between clients and vehicles between suppliers is rare.
F5 CREATEADS
In most files other files, NEOSYS only stores the main codes like brand code and vehicle code and every time a report needs the client or supplier code it looks up that information from the separate brand or vehicle file so it always gets the latest info. This is how databases usually work. Actually some people would like the reports based on the ORIGINAL codes rather than the latest codes.
