SYMENU System Manager Introduction 4

File Format Conversions


Converting Micro Focus ISAM Database to Btrieve


If you are using a Micro Focus ISAM Database, the first thing you need to do is to convert your ISAM files to Btrieve format since Elliott V7 does not support a Micro Focus ISAM database.  Before you run the utility to convert your ISAM database to Btrieve, please make sure Pervasive SQL (2000 or higher) is already installed.  In the directory where you installed Elliott V7 (which will be the same directory that your V6.6/V6.7 data resides), you can use the following command to convert ISAM files to Btrieve format:


            CONVERT DATA


CONVERT is the batch file utility and DATA is the sub-directory where your ISAM database resides.



Convert Btrieve Database to be PSQL Compliant


If you were using a V6.6/V6.7 Btrieve database before or if you were previously using a Micro Focus ISAM database and just converted to Btrieve format, your Btrieve database may not be PSQL compliant.  Report writer or ODBC drivers may not always able to read your data and erroneous results may happen.  This condition is caused by an issue called “Segmented Keys.”  To illustrate this issue, let’s take a look at the COP Order Line Item file.  The primary key for this file consists of two segments:


            Order-No           6 Bytes

            Line-No             3 Bytes


If your Btrieve database shows this file’s primary key as one segment of 9 bytes, then it is “non-segmented.”  It will work fine with the Elliott Business Software, however it may not always work when other applications try to access this database through the PSQL relational database layer.  To resolve this problem, we provide a utility (SQL2BTR.EXE) located in the Elliott root directory (i.e. F:\ELLIOTT7).  To convert the Btrieve files that are in a non-segmented key format to one that is segmented, start a command prompt and from the root directory of Elliott type the following command:


            SQL2BTR DATA


SQL2BTR is the EXE utility and DATA is the sub-directory that contains the non-compliant Btrieve data files.  Please make sure the DDF files (you can find them in \ELLIOTT7\DDF40 directory) are in your data directory before you start the conversion.  Also, PSQL (Version 2000 or higher) client or Workgroup engine needs to be installed before you convert.



Elliott Transaction Control


Application Overview


This section explains how Elliott has implemented Transaction Control (TRX Control) into Elliott Software. TRX Control prevents corruption of major Elliott data files if the system fails during a posting, purging or clearing accumulator operation. When enabled, TRX Control views the operation as a single transaction. If the operation is completed successfully then TRX Control ends the transaction and the Elliott data files are updated. If an error is encountered or the system fails during the operation, TRX Control will perform an “automatic rollback” of the data files updated during the operation. Once the system is functioning again, TRX Control will undo all data file changes made by the operation and return the data files to their original state. When the problem has been corrected then the unsuccessful operation may be run again.


Elliott Software uses explicit transaction tracking. This means that Elliott automatically controls when each transaction is started and ended. Elliott Software will use TRX Control during most posting, purging and clearing of accumulator operations. However, because of design, some purging operations will not use TRX Control.


Trx Considerations


There are basically two considerations that need to be taken into account as to whether TRX Control should be used with Elliott Software. The first consideration is disk space available. When a transaction is started, TRX Control will build a transaction rollback work file that is used until the transaction is aborted or ended. For example, a 2-megabyte transactional data file being updated would require an additional 2 megabytes for the TRX Control work file. TRX Control transaction work files are reused. However, there is a chance that the volume on which the transaction work files are kept will run out of space. The second consideration is performance on transactional data files. There is additional overhead associated with transaction control; therefore, if TRX Control is enabled, the performance of some Elliott Software applications will be affected.



Potential Problems With Trx


The following are potential problems or limitations that may occur if Trx Control is in use with Elliott Software:

           Transaction control cannot guarantee data file integrity if there are disk failures.

           Transaction control cannot span across multiple file servers.

           Performance may be hindered if transaction control is used.


Furthermore, large transactions, like G/L year end closing, may cause the server to crash.  Since G/L year end closing will purge out all prior year data and create a balance forward transaction for each balance sheet account, the process either has to completely finish or back out entirely.  There is no middle point.  If your GLTRXFIL is relatively small (a few meg), you might be OK with trx control on.  However, if your GLTRXFIL is a 50 Meg file, the process to create the rollback file may become very inefficient toward the end and your server may simply running out of resources and crash.  Therefore, you should turn off Trx Control before you start G/L year end closing procedure.  The following are areas that you should turn off Trx control:


General Ledger Year End Closing

Inventory Physical Count Posting

Posting a single trx with more than 500 serial numbers.


Transaction Backout


An active transaction is backed out by the system if the file server fails, the workstation fails or the Elliott application encounters a data file error while the transaction is in progress.  The following can cause a transaction backout:


     Elliott Software encounters a data file error or the Elliott application is terminated abnormally.  This can happen if the user enters CTRL-Break.

           The workstation fails or is re-booted.

           There is no activity between the workstation and the file server for 15 minutes.

           A CLEAR STATION command issued at the file server console.

           A DOWN command issued at the file server console.

           The file server fails or is re-booted.


Failure Recovery


When a crash occurs in the middle of a transaction, the user may not know exactly where the crash occurred and which transaction was backed out.  It is the responsibility of the user to verify the last operation attempted and take any steps necessary to successfully complete it.


Before any workstation can re-enter the Elliott Software system, the transactional flag of the data files must be reset.  Elliott has provided the user with a batch file that will reset all the data file flags.  Follow the steps below to reset all data file flags.


1.                   If the file server did not fail, log out all Elliott users.


2.                   One user should then log into the network as an Elliott user and change directories to the directory where the Elliott system data files are installed.


3.                   At the system prompt, type RSETFLAG<data directory>.  For example, to reset the ELLIOTT\DATA directory, you would type RSETFLAG DATA and press RETURN.  This step is not necessary if you are using the Btrieve file handler.


4.         All Elliott users can now log back into the network.



Installing Trx


The following procedures must be followed in order for the Elliott Software to use transaction tracking:


The Trx Control Flag in Company Setup must be set to Y.


If transaction control is being used, posting applications will be able to access files used by other applications.  Instead of informing the user that the file is currently in use, posting will proceed until a locked record is encountered.  At that point the application will wait until the record is unlocked and then continue.  A possibility of deadlock may happen.  When that happens, we suggest you abort the less critical process (non-posting process) and log back in.  If that does not resolve the record lock situation, you might need to use the Pervasive Control Center utility to clear out the aborted user connection.  If that still does not resolve the record lock problem, then you will have to abort the posting process as well.  Since trx control is on, you should not loose any data when you log back in again.  However, if your post routine still leaves the files open, you will need to use the Pervasive Control Center utility to clear out the connection.



Record Locking


Record locking means temporarily reserving an individual record for access by only one user.  In normal use, this lock is in place for only a few seconds.  An example is the updating of inventory during order entry.  Only one person may allocate any individual inventory item at a time.  Individual inventory items are temporarily locked until they are allocated to line items on an order.  If two data entry persons try to order the same inventory item at the same time, one of the individuals will receive a record locked message.


Record lock messages Vary in both appearance and user response. Examples are:


              Ship Via Code Locked At Another Station – Press RETURN

  A Locked Record Is In The Way Of The Next Operation – Press RETURN

  Record Is Locked At Another Station – Press RETURN

  Customer No XXXXXX Locked At Another Station

  Customer No XXXXXX locked by XXXXXXXXXX


Some programs will allow you to make another selection after pressing the RETURN key in response to the above messages.  Other programs will redisplay the message until the record is cleared.  Users should never leave their station when data is being entered because they may leave a record locked.  If a station is to be left unattended, the user should make sure only a menu is being displayed.  Other examples of locked record messages are:


A Locked Record Is In The Way Of The Next Operation…Please Wait


This message will display until changes to the record are completed at another workstation.


Account Locked At Another Station – Will You Wait ? N


If you answer Y to this question, you will get the same question again until the record clears.  If you answer N you will have an opportunity to view another record.


Customer No XXXXXX Locked At Another Station


Some procedures that process a range of records or an entire data file, like Set Customer Balances, will notify you which record is locked.  Generally, these procedures must continue to process and will check every second to see if the locked record has been released.  By supplying the record information, you can determine who has that particular record locked and ask them to release the record.  Once the record is released, processing will continue.


Customer No XXXXXX locked by XXXXXXXXXX


This is similar to the above lock message, but has been updated to include the user ID.  Once the record is released, processing will continue.



File Locking

File Locking means temporarily reserving an entire file or files for access by only one user.  Setup files and the Company file are always locked when they are updated.  An example of a file lock message is:


Company File Presently In Use


This will be displayed in a window when you try to access an application that needs this file while it is being exclusively used by another application.


The most frequent display of file lock messages is in the use of posting applications.  These programs need exclusive use of certain data files because of the extensive amount of updating that is being done.  We recommend you Defer your posting until after your nightly backup has completed.  By utilizing the Deferred Processing application, the files will be posted at a time when it is convenient to your company.  See the Deferred Processing section of this manual.


If the Btrieve file handler is being used and the Trx Control Flag in Company Setup is set to Y, posting applications will be able to access files that are being used by other applications.  Normally, the File In Use message would be displayed.

Systems Manager

  1. Mapped Drives Disappear After Logoff or Reboot
  2. Using Raw Data Pass Through for Dot Matrix Printer on Windows 10 Does Not Work
  3. How Do I Find The Workstation That's Infected with The Crypto Ransom Ware?
  4. How to Reset the Counter in *.DAT Files After Recovery from Crypto Ransom Ware Attack
  5. Aging Shows Differently After Database Rebuild
  6. What Do I Do When My Anti-virus Software Reports Elliott EXE File as a Virus?
  7. High CPU Usage and Performance Issues After Implementing NTFS Security
  8. "We can't verify who created this file. Are you sure you want to run this file?"
  9. Problem with Printer Configuration If Running Elliott from Multiple Workstations
  10. Inconsistent Elliott Error on Terminal Server
  11. How to Restore Elliott from CryptoWall Ransomware Attack
  12. Clarify Laser Forms Line Item Level Barcode Printing
  13. Is Dot Matrix Printer Still Supported in Elliott with Windows 10?
  14. Should I Install the 32-bit or 64-bit Outlook/Office?
  15. I Receive Error 114 When I Start Up Elliott on the Server
  16. Manage Data Execution Prevention (DEP) Through Registry Editing
  17. Windows Defender May Cause Elliott Start-Up Difficulties
  18. Why Do I Exceed Elliott User License Count When There are No or Very Few Users in Elliott?
  19. What Causes Load Error 198?
  20. How the Windows Scheme You Choose May Affect the Elliott Screen Display
  21. Still Get Error 114 After Adding All Elliott EXE Files to the DEP List
  22. How to Copy Laser Form Templates from Company to Company
  23. Weird Character Displayed for Backslash (\) Character
  24. Does Elliott Support Desktop Virtualization?
  25. Access Is Denied When Launching Elliott V8 Report Viewer
  26. User Cannot See Some Spooled Reports in Elliott V8
  27. Why Does the User List Function Take Forever to Bring Up?
  28. I Am Running Out of Invoice Numbers -- I Need Direction to Archive Invoices
  29. Algorithm to Speed Up eContacts List in Elliott V8
  30. Elliott Requires Volume Supporting 8dot3name
  31. Elliott Running Extremely Slow on Windows 8 with Trend Micro Anti Virus Software Installed
  32. What Causes "File Table Exceed Limit" Error?
  33. Mass Email Time Out
  34. Report Incomplete After 4 Hours: Event Stops Working After Upgrade to Elliott V8
  35. File Created in C:\ Root Directory Disappears
  36. Is There a Way to Create and Distribute Elliott Printer Configurations?
  37. What Are "COBOL Only" or "User Defined" Event Actions? Can We Use Them in Any Way?
  38. How to Purge WSORDHDR.BTR and WSORDLIN.BTR files?
  39. CPORDLS (Order Serial/Lot File) Btrieve Page Size
  40. Create PO Receiving Event to Trap Negative Qty on Hand Problem
  41. Reducing File Sizes for INITLFILE.LOG & SYACTLOG.BTR
  42. Windows 10 and Trend Micro Anti-Virus Software
  43. The Remote Certificate Is Invalid According to the Validation Procedure
  44. Customer Has Multiple Primary Contacts or No Primary Contact
  45. Btrieve Error 46 on S/M Activity Log File
  46. Multi-Currency Workarounds in Elliott
  47. Using the Export Processor to Export Data
  48. Instructions for Importing Laser Form Template
  49. I Am Unable to Post or Enter a Date for the New Year
  50. Does Elliott Work Under Virtualized Desktops Infrastructure (VDI)
  51. Btrieve Error 80 During Defer Processing
  52. Lauch CSV File -- There Was a Problem Sending the Command to the Program
  53. Feature - System Users File Integrity Check
  54. Receive Error in NWSMSCRN for Function Pf-Map-Coordinate-Space
  55. Not Able to Receive Event Emails from Certain Users
  56. Feature - Events for Add Note and Delete Note
  57. When and How to Use DDF2BTR.EXE Utility
  58. Elliott Last Printing Job Overrides Windows Default Printer on Windows 10
  59. Not Able to Change Attributes Added by Other Users
  60. Feature - New Context Menus in v8.0 Spooled Reports Manager
  61. Feature - Automatic Archiving of Spooled Reports in Elliott v8.0
  62. Feature - Enhanced Security for Attributes
  63. Feature - Deferred Processing Multiple Times Per Day
  64. Feature - Ability to Specify User ID in User Search
  65. Feature - Utility to Re-Calculate Item First Received and Last Received Date
  66. NSCTLMN1 Global Setup Time Clock Global Setup
  67. How to Set Up One-to-One Restriction of Customer and Item
  68. Recursion Error When Drill Down to Item File Inquiry
  69. Error Invoking Macro - Cannot Install Hook
  70. Feature - Record Navigation in Attribute Window
  71. Error Connecting VPN from Windows 10 to Windows 2008 Server
  72. How to Stop Users from Sending Elliott Reports through Email
  73. Does Elliott Support Windows 10?
  74. It Is Extremely Slow to Run Elliott over VPN Connection
  75. SYTIMCLK Systems Manager General Time Clock
  76. Feature - Recalculate AP Vendor YTD and Last Year Amount
  77. XCO0100 Systems Manager Design Your Own Order
  78. Feature - Restrict Recurring Event for Number of Times for a Specific Reference
  79. How Do I Limit the Companies for Users?
  80. Feature - Enforced Report Destinations
  81. I Am Unable to Create a New User in Elliott
  82. Feature - PDF Printing in Elliott V8.2
  83. Feature: PDF PostOffice in Elliott V8.2, Introduction
  84. Feature: PDF PostOffice in Elliott V8.2, Part 1
  85. Feature: PDF PostOffice in Elliott V8.2, Part 2
  86. Feature: PDF PostOffice in Elliott V8.2, Part 3
  87. Feature - Added Checkbox and Description to Attribute List and the SPS Commerce Create Attribute Register
  88. Feature - Performance Options for eContact Activity Tab
  89. Feature - Mass Change Salesman Utility
  90. Elliott Installer File-In-Use Warning During Installation
  91. Unable to Run Elliott from UNC Path
  92. V8 Program Desktop Startup Shortcuts - Internal Macro
  93. Event When Order Put On Hold at Invoice Printing
  94. Feature - Time Clock Logoff Type
  95. Feature - Added Distribution to G/L History Files
  96. Feature - Utility to Update eContact PDF PostOffice Flags
  97. Can I Use Elliott for Sales, Telemarketing and CRM Purposes?
  98. Emailing PDF with SSPI Failed After Online Charging Using Credit Card
  99. Can You Explain How Elliott Stores Serial Numbers in Its Database?
  100. Converting Elliott Internal Date to Conventional Date Format in Excel
  101. All of a Sudden, My Terminal Server's Elliott Default Changed to Someone Else's Settings
  102. WannaCry Ransomware Security Recommendation
  103. Symantec Endpoint Protection Versions 12 and 14 Cause Elliott Startup Error
  104. Notes Security - From Global Setup, Note Type to Supervisory Relationship
  105. Remote Desktop Workstation Name
  106. Which Anti-Virus Software Do You Recommend to Installing on the Elliott ERP Server?
  107. Menu Access Error - You Do Not Have Access to CP,INQ, Menu Item 01
  108. Ping Test to Isolate Inconsistent Load Error 198
  109. The Definitions of Extra Flags in System Period Control Setup
  110. How to Use Procdump.exe to Create a Memory Dump for PSQL Engine
  111. Feature - Group Location Security
  112. NSCTLMN4 Global Setup Bill of Lading 1
  113. NSCTLMN4 Global Setup Bill of Lading 2
  114. NSCTLMN4 Global Setup Bill of Lading 3
  115. NSCTLMN4 Global Setup Bill of Lading 4
  116. NSCTLMN4 Global Setup Bill of Lading 5
  117. NSCTLMN4 Global Setup Bill of Lading 6
  118. NSCTLMN4 Global Setup Bill of Lading 7
  119. NSCTLMN4 Global Setup Bill of Lading 8
  120. NSCTLMN4 Global Setup Bill of Lading 9
  121. NSCTLMN4 Global Setup Bill of Lading 10
  122. NSCTLMN4 Global Setup Bill of Lading: Index
  123. Feature - Support 12 Months History in Export Processor
  124. NSCTLMN3 Inventory Management Global Control Setup 1
  125. NSCTLMN3 Inventory Management Global Control Setup 2
  126. NSCTLMN3 Purchase Order Global Control Setup 1
  127. NSCTLMN3 Purchase Order Global Control Setup 2
  128. NSCTLMN3 Bill of Material and Production Order Global Control Setup
  129. NSCTLMN3 Distribution Modules Global Setup: Index
  130. NSCTLMN5 Global Setup Change Quote to Order 1
  131. NSCTLMN5 Global Setup Change Quote to Order 2
  132. NSCTLMN5 Global Setup Change Quote to Order 3
  133. NSCTLMN5 Global Setup Change Quote to Order 4
  134. NSCTLMN5 Global Setup Change Quote to Order 5
  135. NSCTLMN5 Global Setup Change Quote to Order 6
  136. NSCTLMN5 Global Setup Change Quote to Order: Index
  137. I Cannot See the Spooled Reports Even though I Am an Administrator Equivalent User
  138. Multi-Currency Exchange Handling in Elliott
  139. How to be a Good Elliott Citizen
  140. Salesman Security
  141. SYMENU System Manager Introduction 1
  142. SYMENU System Manager Introduction 2
  143. SYMENU System Manager Introduction 3
  144. SYMENU System Manager Introduction 4
  145. SYMENU System Manager Introduction 5
  146. SYMENU System Manager Introduction 6
  147. SYMENU System Manager Introduction 7
  148. SYMENU System Manager - External Macros
  149. SYMENU System Manager - Internal Macros
  150. SYMENU System Manager Introduction 10
  151. Feature - Audit Trail of Accumulator Clearing
  152. SYMENU System Manager Introduction 11
  153. SYMENU System Manager Introduction 12
  154. SYMENU System Manager Introduction 13
  155. SYMENU System Manager Introduction 14
  156. SYMENU System Manager Introduction 15
  157. SYMENU System Manager Introduction 16
  158. SYMENU System Manager Introduction 17
  159. SYMENU System Manager Introduction 18
  160. SYMENU System Manager Introduction 19
  161. SYMENU System Manager Introduction 20
  162. SYMENU System Manager Introduction 21
  163. SYMENU System Manager Introduction 22
  164. SYMENU System Manager Introduction 23
  165. SYMENU System Manager Introduction 24
  166. SYMENU System Manager Introduction 25
  167. SYMENU System Manager Introduction 26
  168. SYMENU System Manager Introduction 27
  169. SYMENU System Manager Introduction 28
  170. SYMENU System Manager Introduction 29
  171. SYMENU System Manager Introduction 30
  172. SYMENU System Manager Introduction 31
  173. SYMENU System Manager Introduction 32
  174. SYMENU System Manager Introduction 33
  175. SYMENU System Manager Introduction 34
  176. SYMENU System Manager Introduction 35
  177. SYMENU System Manager Introduction 36
  178. SYMENU System Manager Introduction 37
  179. SYMENU System Manager Introduction 38
  180. SYMENU System Manager Introduction 39
  181. SYMENU System Manager Introduction 40
  182. SYMENU System Manager Introduction 41
  183. SYMENU System Manager Introduction 42
  184. SYMENU System Manager Introduction 43
  185. SYMENU System Manager Introduction 44
  186. SYMENU System Manager Introduction 45
  187. SYMENU System Manager Introduction 46
  188. SYMENU System Manager Introduction 47
  189. SYMENU System Manager Introduction 48
  190. SYMENU System Manager Introduction 49
  191. SYMENU System Manager Introduction 50
  192. SYMENU System Manager Introduction 51
  193. SYMENU System Manager Introduction 52
  194. SYMENU System Manager Introduction: Index
  195. Elliott V7.0 Release Notes: What's New Since Elliott V6.7
  196. Elliott V7.1 Release Notes: What's New Since Elliott V7.0
  197. Elliott V7.2 Release Notes: What's New Since Elliott V7.1
  198. Elliott V7.3 Release Notes: What's New Since Elliott V7.2
  199. Elliott V8.1 Release Notes: What's New Since Elliott V8.0
  200. Elliott V7.4 Release Notes: What's New Since Elliott V7.3
  201. Elliott V7.5 Release Notes: What's New Since Elliott V7.4
  202. Elliott V8.0 Release Notes: What's New Since Elliott V7.5
  203. Elliott V8.2 Release Notes: What's New Since Elliott V8.1
  204. Drill Down and Receive Message You Do Not Have Access
  205. Problem Running Elliott After Upgrading Windows 10 to Fall Creator Edition
  206. MAPISendMail failed! Not supported [26]
  207. What Information Is Stored in System 12 Months Table (SY12MONS)?
  208. Elliott Telephony Integration - How to Call through My Telephone Set from eContact?
  209. Error Adding Printer Configuration After Latest Windows 10 Update
  210. Anti-Virus Causes PostOffice Emailing Problem
  211. Feature - Equal Sign Support in Export Processor
  212. Running Elliott 8.2 and Up on Windows 2003 Server
  213. How Can I Find Out About New Elliott Events Added or Changed Lately?
  214. Feature - Export Enhanced Attribute Predefined Code Value and Description
  215. Error 114 with GUIUTL32.LBR\ in Defer Processing
  216. EL800.EXE - Bad Image - MSVCRT20.dll Is Either Not Designed to Run on Windows or It Contains an Error
  217. Anti-Virus Caused Failure on Crystal Reports ODBC Access
  218. AVIRA Anti Virus Software Kills Elliott EL800 Executable
  219. Error: Trx Date Outside Date Range (00/00/00 - 00/00/00)
  220. How to Allow User to See All Spooled Reports in One Module
  221. A Support Case of Investigating Elliott Database Performance Problem
  222. Received Error in Macro DEALLOC-SHR-MEM Deallocate Failed - Invalid Pointor
  223. Feature - Added the Ability to Purge the System Activity Log

Feedback and Knowledge Base