POS Auto Relicense

2012-06-17T23:10:25Z

Bevan:

File:Auto Relicense Figure 1.jpg

2012-06-17T23:09:06Z

Bevan: uploaded a new version of "File:Auto Relicense Figure 1.jpg": Smaller

Auto relicensing Enabler setup screen shot

File:Auto Relicense Figure 1.jpg

2012-06-17T23:08:11Z

Bevan: Auto relicensing Enabler setup screen shot

Auto relicensing Enabler setup screen shot

2009-10-26T05:17:15Z

Bevan:

Created: 26 October 2009. Last Reviewed: 26 October 2009

Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. Enabler allows certain parameters that control the operation of the BDE to be configured. These settings are written by Enabler to the Registry, where the BDE looks for its configuration.

These settings in Enabler are found in Configuration / Database Setup on the tab titled “BDE Settings”:

[[Image:BDE_Advanced_Settings_Figure1.jpg]]

Enabling the use of advanced settings and using the Recommned Settings (click Recommended Settings) can yield quite substantial performance improvements compared with the BDE default settings that would otherwise be used. The settings specified in this screen take affect only when:

# The new settings have been successfully written to the Registry
# All BDE client applications (including Enabler POS, Back Office and Nibbler) have been closed and restarted. Sometimes it is easier to restart the machine to be sure.

=== Writing Settings to the Registry ===
The Registry key '''HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\Settings\SYSTEM\INIT''' might be secured such that POS logins cannot write to it. This can be determined by clicking the Test Registry Access button from the BDE settings screen on each terminal. Remember, however, that although you might have Registry Access when configuring these settings on your Enabler head office server, store machines might ''not'' have appropriate registry access. In order to allow the settings to be written to the Registry, you might have to log in as an administrator account ''one time only'' and load Enabler. Enabler would update the registry as it loads, and because the Registry data is in HKLM, not HKCU, this setting will continue to apply once you resume your normal Windows login.

=== Testing Impact of These Settings ===
As these settings change the memory footprint of the BDE, you might have to experiment with alternative BDE shared memory address settings. Once these changes have been made, verify that Enabler still runs without displaying error messages relating to BDE memory. It is important to verify that POS and Nibbler can both run, no matter which order they are loaded (POS first vs Nibbler first). For servers, try loading Back Office as well.

Note that if you have multiple machine types, configurations or Windows versions, you should test and verify these new settings on each platform.

File:BDE Advanced Settings Figure1.jpg

2009-10-26T05:17:02Z

Bevan:

BDE Advanced Settings

2009-10-26T05:16:28Z

Bevan: New page: Created: 26 October 2009. Last Reviewed: 26 October 2009 Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. Enabler allows...

Created: 26 October 2009. Last Reviewed: 26 October 2009

Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. Enabler allows certain parameters that control the operation of the BDE to be configured. These settings are written by Enabler to the Registry, where the BDE looks for its configuration.

These settings in Enabler are found in Configuration / Database Setup on the tab titled “BDE Settings”:

[[Image:]]

Enabling the use of advanced settings and using the Recommned Settings (click Recommended Settings) can yield quite substantial performance improvements compared with the BDE default settings that would otherwise be used. The settings specified in this screen take affect only when:

# The new settings have been successfully written to the Registry
# All BDE client applications (including Enabler POS, Back Office and Nibbler) have been closed and restarted. Sometimes it is easier to restart the machine to be sure.

=== Writing Settings to the Registry ===
The Registry key '''HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\Settings\SYSTEM\INIT''' might be secured such that POS logins cannot write to it. This can be determined by clicking the Test Registry Access button from the BDE settings screen on each terminal. Remember, however, that although you might have Registry Access when configuring these settings on your Enabler head office server, store machines might ''not'' have appropriate registry access. In order to allow the settings to be written to the Registry, you might have to log in as an administrator account ''one time only'' and load Enabler. Enabler would update the registry as it loads, and because the Registry data is in HKLM, not HKCU, this setting will continue to apply once you resume your normal Windows login.

=== Testing Impact of These Settings ===
As these settings change the memory footprint of the BDE, you might have to experiment with alternative BDE shared memory address settings. Once these changes have been made, verify that Enabler still runs without displaying error messages relating to BDE memory. It is important to verify that POS and Nibbler can both run, no matter which order they are loaded (POS first vs Nibbler first). For servers, try loading Back Office as well.

Note that if you have multiple machine types, configurations or Windows versions, you should test and verify these new settings on each platform.

Product Indexes

2009-10-26T04:59:27Z

Bevan:

Created: 26 October 2009. Last Reviewed: 26 October 2009

Enabler uses indexes to assist in rapidly retrieving data from the database. These indexes work just like an index in a book – the search value is located in the index, and the index tells Enabler where in the database to look for the full data record. Indexes are essential to allow data to be retrieved rapidly, however they require work to maintain. Every time new information is added to the database, the index must be updated to tell Enabler how to retrieve that data.

Tables in Enabler may be indexed on many different fields or combinations of fields. For example, the product table is indexed by product code, barcode, description, supplier product code and many more fields. Thus for each product that is added to Enabler, all these indices must also be maintained.

The product table is perhaps the most important table in Enabler, in so far as products are central to most POS operations. As a result, the product table, and to a degree the style table, tend to have a large number of indexes. It is also common, for the product table in particular, to have quite a large number of rows in these tables – product tables with > 600,000 rows are not uncommon.

Because of the large number of rows and the large number of indexes, it follows that if some of these indexes can be disabled, substantial performance gains can be enjoyed when importing new/additional products into the Enabler product database.

A tab exists in the Product Database Options called “Index Options”.

[[Image:Product_Indexes_Figure1.jpg]]

On this tab, you can turn off various indexes on the posprod & posstyle tables. The more products you have, the slower it becomes due to the number of indexes that need to be updated, even if you are not using a lot of them. Turning off indexes that you do not use will have a significant impact on the time taken importing new products.

The functional impact of turning off the indexes differs depending on the index in question. A summary is below. Note that in all cases where it says cannot search from PLU prompt, this also applies to other areas of Enabler as well where we search for a PLU, not just the sales screen (i.e product field on stock adjustments or product labels screens). This is because the underlying product lookup logic has been changed to ignore those indexes that have been turned off.

=== Product Table (local\posprod.dbf): ===
Turn off supplier stock code 1 index

-When supplier product code 1 is added as a custom field to the product browse, you will no longer be able to sort the browse results via supplier product code 1.

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier code 1 index'''

-Cannot search via supplier code 1 only in the advanced search screen on the product browse.

'''Turn off division index'''

-Cannot search via division code only in the advanced search screen on the product browse.

'''Turn off class index'''

-Cannot search via class code only in the advanced search screen on the product browse.

'''Turn off barcode index '''

-Cannot search from the PLU prompt in the sales screen using the product barcode contained in the product table. Searching via barcodes contained in local\posbarc is still supported. Note: When using barcodes sent form EEE, they are stored in the local\posbarc table, not the local\posprod.pd_barc field.

-When importing SOH (SC records, ISL-INV.DAT), cannot search for product via posprod.pd_barc when barcode included but no PLU included in the import record. The number of attempts that were skipped is logged to the event log, i.e “Product Quantities (no PD_BARC index) = 113”.

-When generating new products from the style maintenance, and the option to generate a barcode is turned on, we do not generate a new barcode

=== Style table (local\posstyle.dbf): ===
'''Turn off supplier stock code 1 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

-No longer an index that can be selected on the style browse.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off barcode index'''

-Cannot search from the PLU prompt in the sales screen using the style barcode contained in the style table.

For example, when “division” index is turned off in the example above, performing an advanced search will not allow you to search on division without entering a class, supplier or department to narrow down the search via index first:

[[Image:Product_Indexes_Figure2.jpg]]

The local\posprod.dbf and local\posstyle.dbf files are always conditionally reindexed during the data purge as part of the end of day. This will force indexes turned on/off to be regenerated/removed. You can off course reindex the files manually, do a conditionalindexall or a migrate to update the indexes to what you have selected.

Product Indexes

2009-10-26T04:59:00Z

Bevan:

Created: 26 October 2009. Last Reviewed: 26 October 2009

Enabler uses indexes to assist in rapidly retrieving data from the database. These indexes work just like an index in a book – the search value is located in the index, and the index tells Enabler where in the database to look for the full data record. Indexes are essential to allow data to be retrieved rapidly, however they require work to maintain. Every time new information is added to the database, the index must be updated to tell Enabler how to retrieve that data.

Tables in Enabler may be indexed on many different fields or combinations of fields. For example, the product table is indexed by product code, barcode, description, supplier product code and many more fields. Thus for each product that is added to Enabler, all these indices must also be maintained.

The product table is perhaps the most important table in Enabler, in so far as products are central to most POS operations. As a result, the product table, and to a degree the style table, tend to have a large number of indexes. It is also common, for the product table in particular, to have quite a large number of rows in these tables – product tables with > 600,000 rows are not uncommon.

Because of the large number of rows and the large number of indexes, it follows that if some of these indexes can be disabled, substantial performance gains can be enjoyed when importing new/additional products into the Enabler product database.

A tab exists in the Product Database Options called “Index Options”.

[[Image:]]

On this tab, you can turn off various indexes on the posprod & posstyle tables. The more products you have, the slower it becomes due to the number of indexes that need to be updated, even if you are not using a lot of them. Turning off indexes that you do not use will have a significant impact on the time taken importing new products.

The functional impact of turning off the indexes differs depending on the index in question. A summary is below. Note that in all cases where it says cannot search from PLU prompt, this also applies to other areas of Enabler as well where we search for a PLU, not just the sales screen (i.e product field on stock adjustments or product labels screens). This is because the underlying product lookup logic has been changed to ignore those indexes that have been turned off.

=== Product Table (local\posprod.dbf): ===
Turn off supplier stock code 1 index

-When supplier product code 1 is added as a custom field to the product browse, you will no longer be able to sort the browse results via supplier product code 1.

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier code 1 index'''

-Cannot search via supplier code 1 only in the advanced search screen on the product browse.

'''Turn off division index'''

-Cannot search via division code only in the advanced search screen on the product browse.

'''Turn off class index'''

-Cannot search via class code only in the advanced search screen on the product browse.

'''Turn off barcode index '''

-Cannot search from the PLU prompt in the sales screen using the product barcode contained in the product table. Searching via barcodes contained in local\posbarc is still supported. Note: When using barcodes sent form EEE, they are stored in the local\posbarc table, not the local\posprod.pd_barc field.

-When importing SOH (SC records, ISL-INV.DAT), cannot search for product via posprod.pd_barc when barcode included but no PLU included in the import record. The number of attempts that were skipped is logged to the event log, i.e “Product Quantities (no PD_BARC index) = 113”.

-When generating new products from the style maintenance, and the option to generate a barcode is turned on, we do not generate a new barcode

=== Style table (local\posstyle.dbf): ===
'''Turn off supplier stock code 1 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

-No longer an index that can be selected on the style browse.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off barcode index'''

-Cannot search from the PLU prompt in the sales screen using the style barcode contained in the style table.

For example, when “division” index is turned off in the example above, performing an advanced search will not allow you to search on division without entering a class, supplier or department to narrow down the search via index first:

[[Image:]]

The local\posprod.dbf and local\posstyle.dbf files are always conditionally reindexed during the data purge as part of the end of day. This will force indexes turned on/off to be regenerated/removed. You can off course reindex the files manually, do a conditionalindexall or a migrate to update the indexes to what you have selected.

Product Indexes

2009-10-26T04:50:34Z

Bevan:

Created: 26 October 2009. Last Reviewed: 26 October 2009

Enabler uses indexes to assist in rapidly retrieving data from the database. These indexes work just like an index in a book – the search value is located in the index, and the index tells Enabler where in the database to look for the full data record. Indexes are essential to allow data to be retrieved rapidly, however they require work to maintain. Every time new information is added to the database, the index must be updated to tell Enabler how to retrieve that data.

Tables in Enabler may be indexed on many different fields or combinations of fields. For example, the product table is indexed by product code, barcode, description, supplier product code and many more fields. Thus for each product that is added to Enabler, all these indices must also be maintained.

The product table is perhaps the most important table in Enabler, in so far as products are central to most POS operations. As a result, the product table, and to a degree the style table, tend to have a large number of indexes. It is also common, for the product table in particular, to have quite a large number of rows in these tables – product tables with > 600,000 rows are not uncommon.

Because of the large number of rows and the large number of indexes, it follows that if some of these indexes can be disabled, substantial performance gains can be enjoyed when importing new/additional products into the Enabler product database.

A tab exists in the Product Database Options called “Index Options”.

[[Image:Product_Indexes_Figure1.jpg]]

On this tab, you can turn off various indexes on the posprod & posstyle tables. The more products you have, the slower it becomes due to the number of indexes that need to be updated, even if you are not using a lot of them. Turning off indexes that you do not use will have a significant impact on the time taken importing new products.

The functional impact of turning off the indexes differs depending on the index in question. A summary is below. Note that in all cases where it says cannot search from PLU prompt, this also applies to other areas of Enabler as well where we search for a PLU, not just the sales screen (i.e product field on stock adjustments or product labels screens). This is because the underlying product lookup logic has been changed to ignore those indexes that have been turned off.

Product Table (local\posprod.dbf):'''Turn off supplier stock code 1 index'''

-When supplier product code 1 is added as a custom field to the product browse, you will no longer be able to sort the browse results via supplier product code 1.

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code.

-Centralised Purchase Orders. Cannot validate/resolve a PLU entered using “.” Notation to search for a supplier stock code.

'''Turn off supplier code 1 index'''

-Cannot search via supplier code 1 only in the advanced search screen on the product browse.

'''Turn off division index'''

-Cannot search via division code only in the advanced search screen on the product browse.

'''Turn off class index'''

-Cannot search via class code only in the advanced search screen on the product browse.

'''Turn off barcode index '''

-Cannot search from the PLU prompt in the sales screen using the product barcode contained in the product table. Searching via barcodes contained in local\posbarc is still supported. Note: When using barcodes sent form EEE, they are stored in the local\posbarc table, not the local\posprod.pd_barc field.

-When importing SOH (SC records, ISL-INV.DAT), cannot search for product via posprod.pd_barc when barcode included but no PLU included in the import record. The number of attempts that were skipped is logged to the event log, i.e “Product Quantities (no PD_BARC index) = 113”.

-When generating new products from the style maintenance, and the option to generate a barcode is turned on, we do not generate a new barcode

Style table (local\posstyle.dbf):

'''Turn off supplier stock code 1 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

-No longer an index that can be selected on the style browse.

'''Turn off supplier stock code 2 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off supplier stock code 3 index'''

-Cannot search from the PLU prompt in the sales screen using “.” notation to search for a supplier stock code of the style.

'''Turn off barcode index'''

-Cannot search from the PLU prompt in the sales screen using the style barcode contained in the style table.

For example, when “division” index is turned off in the example above, performing an advanced search will not allow you to search on division without entering a class, supplier or department to narrow down the search via index first:

[[Image:Product_Indexes_Figure2.jpg]]

The local\posprod.dbf and local\posstyle.dbf files are always conditionally reindexed during the data purge as part of the end of day. This will force indexes turned on/off to be regenerated/removed. You can off course reindex the files manually, do a conditionalindexall or a migrate to update the indexes to what you have selected.

File:Product Indexes Figure2.jpg

2009-10-26T04:49:07Z

Bevan:

2009-04-14T00:49:49Z

Bevan:

Created: 14 April 2009. Last Reviewed: 14 April 2009

=== Table StockMovementTbl Cost and Gross Profit Columns ===
The stock movement table contains a row for every movement of stock, including a row assocaited with every sale or return line item. Except in complex cases such as multi-packs and kits, there is a 1 : 1 relationship between rows in SaleLine and StockMoveTbl. However, not all stock movement rows have associated SaleLine rows – consider stock receipts, transfers etc.

Note columns prefixed with FC are in the currency local to the branch (for EEE instances supporting branches in different countries). The Non-FC version of the column has the amount in the local currency of EEE as converted using user-defined exchange rates.

The population of cost and gross profit columns in table StockMovementTbl for stock movements associated with sales is:

'''Cost'''

FCCost * ExchangeRate

'''TotalCost'''

This is an SQL Server computed column: isnull (ActualTotalCost, Cost*Quantity)

'''FCCost'''

SQL Server stored procedure UpdateStock looks up the configuration for the branch to determine that branch's stock valuation configuration option – i.e. WAC or list cost. Based on this configuration, the current cost for the Branch/SKU is retrieved. If this is null of $0.00, uses BuyPrice1 for the branch/SKU.

Finally, any oncost amount passed back from POS is added to this cost, however for sales POS will always return oncost of $0.00.

'''FCTotalCost'''

This is an SQL Server computed column: isnull (FCActualTotalCost, FCCost*Quantity)

'''OnCost'''

This is populated with the unit on-cost amount passed back from POS, always $0.00 for sales.

'''ActualTotalCost'''

FCActualTotalCost * ExchangeRate

'''FCActualTotalCost'''

FCCost * Qty.

'''AlternateGPCost'''

Cost.AlternateGPCost except client code 22 which uses BuyPrice1 for warehouse branch

=== View vwSaleLine_GP Cost and Gross Profit Columns ===
This view combines sales data from table SaleLine with stock cost data from table StockMovement to provide the most accurate possible GP reporting. In the column descriptions below, “if available” means if a matching stock movement row is found for the SaleLine. In some cases the StockMovement row might be missing, for example in the minimallyt supported scenario where sales are recognised upon creation of a customer order or layby, but stock is not decremented until the order or layby is completed. In such case there is no StockMovement row to match the Sale, therefore no strictly accurate cost or GP is available.

'''ExtendedCostAmount'''

If available, StockMovementTbl.TotalCost else SaleLine.ExtendedCostAmount.

'''GrossProfit'''

If available, SaleLine.ExtendedNetAmount – SaleLine.ExtendedTaxAmount – StockMovementTbl.TotalCost else SaleLine.GrossProfit.

'''FCExtendedCostAmount'''

If available, StockMovementTbl.FCTotalCost else SaleLine.FCExtendedCostAmount

'''FCGrossProfit'''

If available, SaleLine.FCExtendedNetAmount – SaleLine.FCExtendedTaxAmount – StockMovementTbl.FCTotalCost else SaleLine.FCGrossProfit.

'''ExtendedAlternateGPCostAmount'''

StockMovementTbl.AlternateGPCost * SaleLine.Quantity. However if this is NULL, as will be the case when Cost.AlternateGPCost is null, then SaleLine.ExtendedCostAmount except for client code 22 which uses Cost.BuyPrice1 for branch 99 * SaleLine.Quantity.

'''GrossProfitAlternateGP '''

SaleLine.FCExtendedNetAmount – SaleLine.FCExtendedTaxAmount – ExtendedAlternateGPCost.

= See Also: =
[http://theoracle.magentaretail.com.au/wiki/index.php/BDE_Versions ]

Gross Profit and Cost Column Definitions

2009-04-14T00:49:11Z

Bevan: New page: Created: 14 April 2009. Last Reviewed: 14 April 2009 === Table StockMovementTbl Cost and Gross Profit Columns === The stock movement table contains a row for every movement of stock, inc...

BDE Versions

2009-03-16T05:20:24Z

Bevan:

BDE Conflicts

2009-03-16T05:19:25Z

Bevan: New page: Created: 16 March 2009. Last Reviewed: 16 March 2009 Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. The BDE is a commo...

Created: 16 March 2009. Last Reviewed: 16 March 2009

Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. The BDE is a common, shared program component which may be utilitised by other applications.

It is possible for the BDE to enter a temporary, unstable state. This may occur if one Enabler application terminates (or is terminated) abnormally, preventing it from properly disconnecting from the BDE. We have also observed upon rare occasions that third party applications that use the BDE may prevent Enabler from accessing the BDE. This has been observed in relation to a service known as “Insight Manager” which is part of a server monitoring toolset from HP.

=== Symptoms: ===
# Enabler applications already running may freeze and become totally unresponsive. Typically the application is consuming no CPU resource when viewed in Task Manager.
# Enabler applications may fail to load. Upon attempting to start an Enabler application, nothing appears to happen. In Task Manager the EXE can be seen in the process list. The application user interface is never displayed.
# In these cases, the BDE Administration Utility (BDEADMIN.EXE) is generally also unable to be loaded.

=== To Resolve This Issue: ===
# Forcibly close any Enabler applications from Task Manager process list:
## Press Shift+Ctrl+ESC to invoke Task Manager, or use Ctrl+ALT+DELETE and choose Start Task Manager.
## Locate NIBBLE.EXE, WINPOS.EXE and INFOCTRL.EXE. ''Hint: Click image name at the top of the list to sort alphabetically. ''
## For each the above processes found, click the image name in the process list then click End Process (and confirm when prompted).
## Double-check to ensure all the above processes have been removed from the process list.
## If any other processes are known to use the BDE, close those programs or forcibly terminate through Task Manager (forcibly terminate third party applications at your own risk!).
## Try starting Enabler applications as normal.
# If the problem is not resolved or if you have reason to suspect that some other application may be using the BDE:
## Obtain Process Explorer (PROCEXP.EXE) from Sys Internals ([http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx][http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx)/ )].
## Run procexp.exe
## From the Find menu, choose “Find File Handle or DLL”
## At the “Handle or dll substring” prompt enter IDAPI32.DLL and click Search.
## If any process is using the BDE, it will be listed in the search results. The search may take a minute or two to complete.
## If any processes are shown, identify the application that owns the process and try to stop the application. Note – the BDE can also be used by Windows services. Note – the process that directly accesses the BDE might be a child process of the offending application. Check if the listed process(es) has a parent process.
## If necessary, you might have to forcibly terminate such processes. Do this at your own risk!
## Retry the Enabler applications.
## When third party applications are found to conflict with Enabler, you may need to contact Magenta to discuss your options.

= See Also: =
[http://theoracle.magentaretail.com.au/wiki/index.php/BDE_Versions BDE Versions].

BDE Versions

2009-03-16T05:18:42Z

Bevan:

BDE Versions

2009-03-16T05:12:30Z

Bevan:

BDE Versions

2009-03-16T05:02:52Z

Bevan: