Database Builder

Simple Database Builder

The standard Database Builder service enables the remote creation and editing of asset and ID databases stored on codeREADr’s servers. This feature requires connectivity to the Internet via 3G/4G or Wi-Fi. Applications include:

Event Entry/Re-Entry
You would use your primary event access control service to control entry to the event. When an attendee leaves, you can optionally scan their ticket with a separate Database Builder service. That service should be associated to the same database as the primary service. This will allow you to control re-entry to the event. Your app user would scan the departing attendee’s ticket and change the status from Invalid to Valid. In this way when the ticket is again scanned by the primary service it will be Valid. [Note: There are other ways to achieve this goal. Contact support if you have any questions.]

Asset Tagging

Scan the barcode value on an asset (or attach one, if there’s not one on it already) and then enter associated text to describe that asset – we call it ‘Response’ text. When that scan is submitted to our servers it is added to your asset database or, if the asset was already in there, then it will replace the Response text previously associated with it.

Asset Status – Condition / Location / Other

The process is the same as for Asset Tagging but here you would update (edit) the Response text to indicate the current condition or location of the asset.


If you create your own barcode tags (labels) using 2D barcodes (e.g. QR, Data Matrix or PDF-417) and embed descriptive information in those barcodes, then the Response text can be used solely for status updates.

Database Builder is ideal for applications needing to directly update your asset or ID validation database. The trade off with this simple builder is the app-user input can only input text to a single form field.

Alternatively, when using a standard Record Scans service type you can prompt the app-user for multiple form entries, secondary scans, photos, signatures, GPS locations, etc. with each scan. However, this Records Scans data does not update directly to your validation database; instead, you need to export those scan records and re-import them to your database unless you use the Postback option (see below).

Database Builder Screen Shots

if database item exists

if database item does not exist

Database Options

1. Insert to External Databases
If you already have a database hosted on your desktop, your own servers or other external databases, you can:

a) Export, filter and share scan records in template form using the codeREADr ‘Scans’ page and then import those records into your external database(s).

b) Auto-insert scan records into those external databases.

c) Schedule filtered uploads via FTP/SFTP and exports via email.

d) Developers can use Postback, DSU and our API.

2. Advanced Database Builder (DBB Postback)
With the simple Database Builder service, your scans are inserted into the validation database associated to that service. To overcome the simple versions limit to a single form field, you can use our advanced Database Builder with Postback. Using that version your app users can:

a) Scan barcodes and be prompted to enter data based on a wide range of prompts you configure for the service. The resulting record will be added to the validation database.

b) When the app user subsequently scans those barcodes they can view and update the previously entered data.

Please look here for detailed instructions on database builder with postback.

in Databases