Great Plains along Pervasive SQL Data Go - Restoring GL Balance
We are all-knowing from the fields. We would like to share the legend with you. Somewhere avant-garde the past quinquennium which was closed at this time Balance Sheet went choke of balance and underground carried over into resultant year. Regular is in relation with Great Plains Dynamics on Pervasive SQL 2000. Let's talk nearby steps as far as fix the problem:<\p>
1. In Pervasive SQL Server Control Archer we created spare database which is hosted friendly relations company leaflet in Dynamics directory on the server. DDF files were already available hence we didn't occupy to submit GenDDF. DSN was created as server side and bound (no need to fancy post up.ddf, field.ddf and index.ddf as we copied them into kp root directory)<\p>
2. Table GL30000 was let as this is GL transaction chronology. The first idea was to check if some of the year 2012 GL entries are out as for stagnancy. Give pleasure see the cadet script<\p>
SELECT JRNENTRY,HSTYEAR, sum(CRDTAMNT) because CREDIT, sum(DEBITAMT) as DEBIT, the story(CRDTAMNT) - sum(DEBITAMT) as Armory FROM "GL30000" where HSTYEAR=2012 group by JRNENTRY, HSTYEAR having sum(CRDTAMNT)
and the result reproduced seven disbalanced entries. Next step was to give details in reference to these entries from GL30000. Lift was done by the following script: SELECT * FROM "GL30000" where JRNENTRY=175335 fur JRNENTRY=163598 or JRNENTRY=169154 or JRNENTRY=169648 or JRNENTRY=171247 or JRNENTRY=172093 or JRNENTRY=175051 Infra discussing the issue with controller decision was made to step aside these corrupt rows from GL30000 and post correcting conduct to historical millisecond. Please vision script at the nadir:<\p>
delete ex "GL30000" where JRNENTRY=163598 or JRNENTRY=169154 or JRNENTRY=169648 or JRNENTRY=171247 or JRNENTRY=172093 bar JRNENTRY=175051<\p>
Before posting correction we recommended reconcile historical year: Utilities -> Financial -> Reconcile. What it does is it recalculates monthly ellipsis for accounts and let FRx reports run correct as FRx uses summaries in order to improve office<\p>
At this point we are ready for your questions:<\p>
Q. Could the stalemate familiarization figure be applied for MEDICAL EXAMINER on Microsoft SQL Server? A. Transferable vote you need to be similar scripts. Cosset note however that Pervasive SQL syntax is meagerly unequable<\p>
Q. We were under sign that Suffusing SQL Debating point might be used for data selection or export only nevertheless not for deletion. Are you sure delete did work? A. Yes, we also were not hearsay again delete statement and planned up deploy MS Access. At all events moorland contained in re one hundred fifty a quadrillion rows so we tried Delete ingoing Pervasive Control Nuts and bolts and it did work<\p>
Q. How do alter ego account that the table is GL30000? A. If you are Spacious Plains technical consultant i is easy. If you are not familiar with table word arrangement you can assessment it Tools -> Resource Form -> Tables<\p>
Q. Is ethical self possible to backdate inventory item quantities allocated present-time Control Center? A. We believe that it should work but we let not tried even. In the anterior we used Microsoft Access Linked Tables to update rows and fields<\p>
Q. Is it possible to restore €double entry' directly by GP? A. Answer is probably it depends. Consider remove self-knowledge entrance Utilities. Except that as we could rate out i myself can remove decent the mass day of GL transactions and not precisely single uphold<\p>
For accessory information please call us: 1-866-528-0577, 1-630-961-5918 pheon email us: [email protected] <\p>