Read what our customers have to say about our WinWedge and
Bar Code
Software products and support.
TALtech offers a 90-day money back guarantee and free, and unlimited, support for all its software products.
|
 |
|
|
| |
TALtech
Newsletter Issue 40 |
|
|
|
|
 |
| |
|
|
| |
New! May 1, 2007 - WinWedge Standard.
v3.4
WinWedge
easily collects data from devices such as laboratory instruments,
balances, meters, analyzers, sensors, bar code scanners,
GPS receivers and other serial output devices, into any
Windows application. It inputs real-time RS232 (and TCP/IP)
data directly into Excel or any other Windows software.
Use WinWedge to easily perform real-time analysis, charting,
and graphing of your device data in your PC applications.
Multiple instruments can simultaneously send data to different
applications or to different "fields" within the
same application if needed.
This week we are releasing an upgrade to WinWedge Standard.
This upgrade works perfectly with Windows Vista and the latest
versions of Excel. It also includes a re-designed and re-written
help section and manual, new installation program and ability
to minimize to the task bar.
Free Upgrade:
For a free upgrade from your present WinWedge Standard v3.0,
please email your serial number, name and company name
to: sales@TALtech.com.
Download directions will be emailed back to you. The WinWedge
v3.0 configuration files are compatible with the new version
3.4.
|
|
| |
New! February 1, 2007 - WinWedge
Pro v4.0
New features of WinWedge
Pro v4.0 include:
* Improved Installation Program.
* Minimize WinWedge To The System Tray Instead Of To
The Taskbar.
* Send Keystrokes to DOS applications and Citrix Windows
as well as MS Windows applications.
* Re-written user's manual and help files with new
examples for using WinWedge Pro with the latest Windows
application
programs such as the newest versions of Excel.
Upgrade:
If you own any previous version of WinWedge Pro 3.x,
the upgrade cost is $139. The version 3.x configuration
files are completely compatible with version 4.0 so
upgrading is easy. Upgrading from WinWedge Standard
to WinWedge Pro v4.0 is $256.
Please visit the WinWedge page for general information regarding
WinWedge Standard and Pro, application stories and user comments.
|
|
|
|
|
|
|
|
| |
|
| |
Sending and Receiving
Serial Data over the Internet
Are you interested in collecting data from (or sending data to) RS232 devices
at remote locations over the Internet? TALtech’s TCP-Com, RS232 to TCP/IP
redirector software, makes this easy to do. This article gives you the technical
details on how to set this up. More…
|
|
| |
WinWedge and 21CRF11 Compliance
Are you collecting data from laboratory instruments and
that data needs to meet 21CRF11 compliance? This article
explains how WinWedge can be set up as part of your data
collection and data storage system to ensure compliance
with 21CRF11. More…
|
Printing Perfect Bar Codes from
any Printer
Do you need to print perfect bar codes from your office
laser, ink jet and other printers. If so this article
explains how you can ensure that your barcodes will be
readable. It explains why some bar code software and
fonts create poor or unreadable barcodes and how to ensure
that you get perfect barcodes every time. More..... |
|
|
|
|
|
| |
| |
|
|
| |
Tip! Printing
bar codes in Excel spreadsheets
The TAL Bar Code ActiveX control is commonly used for printing
bar codes on documents and labels created in Visual Basic, C++
and Microsoft Access database applications however, it can also
be used to print bar codes in any application that can
host an ActiveX control - including all Microsoft Office applications
like Word and Excel. One of the more powerful features of the
Bar Code ActiveX control is support for "Data Binding" which
allows you to "bind" the bar code "Message" (the
data that you want to encode in your bar codes) to a particular
data field in a "data source" like a table in a database.
For example, if you add the TAL Bar Code ActiveX control to a
Microsoft Access database report, you can set the "Data
Source" property of the control to the name of a field in
the query or table that the report is based on. When you print
the report, the data encoded in the bar code is automatically
pulled from each data record in the query or table as the report
prints. If you insert the Bar Code ActiveX Control on an Excel
spreadsheet, the control will have a "Linked Cell" property
that you can use to bind the bar code message to a specific cell
in the spreadsheet. For example, if you were to set the Linked
Cell property of the TAL Bar Code ActiveX control to "A1",
any data that you enter into cell A1 in the spreadsheet would
automatically be encoded in the bar code and if you change the
data in the cell, the bar code would automatically update itself
encoding the new data.
|
|
| |
Tip! Using
data input forms in Excel while collecting data with WinWedge
The Visual Basic macro language (VBA) in
Excel allows you to create and display custom data input forms
(userforms). One issue
with userforms in Excel is that when a userform is open, the
form blocks all other VBA functions and subroutines from running
until you close the form. Suppose that you are using WinWedge
to feed data from an instrument into an Excel spreadsheet using
Dynamic Data Exchange (DDE) so that the data is collected in
the background. If you were to open a userform, the data collection
would stop because the subroutine that reads in the data from
WinWedge would be blocked from running until you close the form.
Fortunately there is an easy solution to the problem. Starting
in Excel 2000, the Show method for a userform object supports
an optional argument named "modal". If you set the
modal argument to "vbModeless", the userform will be
displayed as a "Non-Modal" form. Basically this means
that other VBA functions and subroutines as well as other userforms
can run while the form is open. For example, suppose that you
have a userform named userform1 and you want to open it as a
Non-Modal form, you could use the following line of code to do
the job: UserForm1.Show vbModeless
Another way to do the same thing is to set the ShowModal property
of the userform to false while you are designing the userform
in the VBA editor.
|
|
| |
Tip! Running
VBA subroutines automatically when you open or close a spreadsheet
Sometimes
it can be handy to have a VBA subroutine run automatically when
you either open or close a
workbook in Excel. For example,
suppose that you would like to display a userform automatically
when a workbook is opened. When you name a VBA subroutine "Auto_Open()",
Excel will automatically run the subroutine when you open the
workbook. Likewise, if you name a subroutine "Auto_Close()",
Excel will automatically run the subroutine when you close the
workbook.
Note: The Auto_Open and Auto_Close subroutines must be stored
in a standard VBA module (not in a worksheet module). To create
a standard VBA module, select Tools - Macro - Visual Basic Editor
and then in the Visual Basic Editor window, select Insert - Module.
You would then type the subroutines into the newly created module.
When you are finished, you would save the module and close the
Visual Basic Editor window to return to Excel's main window.
|
|
| |
|
|
|
|
|
 |
| |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
