Visual DataFlex Blog

RoloFlex PRO 2009 based on VDF 15.0

2009-05-24T12:30:00.000-04:00

I am announcing the release of RoloFlex 2009 due out within 30 days...

RoloFlex Pro 2009 contains upgrades for virtually ALL the suggestions we have had for RoloFlex:

New Features Available Today:
========================
* Import EMail Contacts into RoloFlex from Outlook, GMail, Yahoo, AOL, etc.
* Birthdays of People entry: and reminders
* Customizable categories for attributes [ Source, Category, Rep, Status are all RENAMABLE now ]
* Default the values of the attribues [ Source, Category, Rep, Status ] to make data entry faster
* Default the CITY, STATE, POSTAL, etc.
* Allow PHOTOS of people to be any size .JPG, etc. image (not just small bitmaps)
* Create your OWN Call History Contact Types [ PHONE, MAIL, etc. ]
* Date of Last Contact automatically saved.
* Reports on CONTACT ACTIVITY available.

ALSO: There are many small improvements, touchups, and features such as Microsoft Office MailMerge.

Here is the VIDEO INTRO on RoloFlex PRO : click this link to play the Rolo* Pro Video: Click For RoloFlex2009 Video

As a RoloFlex user, you know that the software is highly effective, reliable, and polished: This is a fantastic new release, packed with features.

All RoloFlex Users will receive an upgrade offer within 30 days.

Regards,
Peter A Donovan
Applause Software of Boston, MA USA

OOPS Proper: What's an obtainable goal for centralized code in Visual DataFlex?

2008-08-11T21:41:00.001-04:00

*Click on image to enlarge please...

OOPS proper coding goal is "no code in objects except property settings", is this obtainable?

The Visual DataFlex Studio and Database Builder utilities are the tools we use to build applications, and the coding style used in actual practice varies from "artist" to "artist" as much as a painting style does.

While the true goal of object oriented style of programming is to truly centralize code, and to produce an application where all customization departure from the basic tools we use should reside in classes, not objects. Further to this, each class has property settings for given or endowed abilities which allow us to re-use the class as instantiated in an object in different settings with different results depending on need.

Here is an example of such "art" in the fact that a module of data entry is first programmed with object code for the desired result, tested.... and then the code is moved to the classes involved for centralization and standardization. Standardization is a fundimental concept where you desire the same behavior in all modules or a programmed variance of same behavior, all set in a central place.

Visual DataFlex allows the programming and testing of object code rather than specifying that all instantiated objects be pure classes.

The "art" to this simple example as illustrated can be taken to many varying ways of implementation. One of the true advantages of VDF is the concept of multiple-inheritance.

Here's the challenge that multiple-inheritance solves:

We have a property setting "Set Auto_Clear_DEO_State to False" and a function SAVEHEADER which really belong both to the cWSdbView and cWSdbModalDialog class as well as possibly a cWSdbTabPage.

Shall we type these into the three classes three times? I think not! Remember our rule of thumb where "when you type code twice, it's time to rethink your methodology", and here's a solution using a MIXIN class. The MIXIN class is "mixed into" a class layer in addition to the regular superclass inheritance. Here's how.

click on image to enlarge please

Visual DataFlex - Organization Foundation

2008-08-11T12:20:00.000-04:00

Visual DataFlex:

an outline:

- Workspace

- Project

- Layers

Workspace:

A Workspace is defined as an organization of resources supporting an application in subfolders defined by the workspace. Standard Layout of a Workspace (with no modification) is;

- AppHtml - .asp code and supporting images plus cascading style sheets, etc.

- AppSrc - windows source code

- Bitmaps - images

- Data

- DDSrc - data dictionary class layers and table definitions

- Help (blank)

- IDESrc - vdf class information

- Programs - executables and workspace definition file plus debugging tracer code

So, with the advent of Vista, and the desire not to place our live app within the PROGRAMS folder, an actual deploy model would look like:

C:\Visual DataFlex Projects\MyWorkspaceName .... with subfolders.

PROJECT: A project is defined as a workspace application (there may be more than one project inside a workspace) executable.

A Project is usually a MDI (multiple dialog interface) application with the following layer structure:

DESKTOP:=================================

- The Desktop is the name for anything outside the inner containers

- The Desktop contains an application object which defines the paths and behaviors associated with the application.

- The Desktop contains: the MAIN panel, the CodeJock skinning, and possbily a Login Panel?

MAIN: ====================================

The Main is a SDI panel which functions as a main container object for the application.

The Main contains the MENU

The Main contains the CLIENT_AREA : the container for interactive modules/objects.

APPCLIENT_AREA:==============================

The APPclient_area is the working ground of all major components of your system.

It contains:

Data Entry Forms

Reports

Selection Lookup Lists

Modal Dialogs

Business Process Objects

Resources such as methods and classes

All Together, the workspace, as described, is designed to let delegation, encapsulation, and polymorphism happen within the context that the modules and sub_objects are arranged.

All Together, it looks like the picture above: click on image for larger view!

Regards,

Peter A Donovan, Applause Software

http://www.applausesoftware.com/

DOS to Windows anyone?

2008-07-29T12:58:00.001-04:00

DOS to Windows Conversion: a facelift?

What advantages does a DOS to Windows Conversion hold, and why should I fix what isn’t broken?

The title and subtitle indicates corporate thinking as I have heard it, from many of the clients I know who have a DOS product fueling their company’s IT needs. The fact of the matter is that there is apprehension to move from a proven software platform. So why invest?

“The most important development in computer technology since the IBM PC”

What was this magazine cover article describing? Not a DOS to windows move! It was describing the onset and implementation of OOPS programming technology that I glanced at while marking time in a company’s waiting room many years ago! More important than nice windows interfaces and gui screen design! The fact is, that both DOS and Windows can be programmed with “Object Oriented Programming Style” but the odds that your DOS program has this structure is very low. Here’s my spin on the top 10 ways this affects your life:

1. Spaghetti Code VS OOPS:
The older style of dos programming has become known as “spaghetti code” when seen in contrast to oops. The basic structure, layout, and philosophy of coding software changed in a wave of approval that is now standard with every modern programming language.

2. Centralized Coding:
The new style of programming impacts your cost to adjust business rules in a huge cost savings factor. The cost savings come mostly by being able to release new versions without unwanted side effects, and also in terms of IT time to create, test, and deploy.

3. Don’t Fix it if it isn’t broke!:
This stand on computer technology was caused by spaghetti code! With “spaghetti code”/DOS standard technology, a change in business rules was feared because it generally caused an upheaval in operations. With DOS standard technology, your system is comprised of hundreds of individual standalone executables running from a menu structure where each of the programs contains duplicate code to perform similar functions along with its look and feel individually set.

4. Training:
Compare the training necessary to learn the function keys that operate DOS with a simple OOPS menu (generally regarded as a windows menu, but also available in dos) where the function you want to perform “enter payments” is listed from a dropdown menu instead of “doing 4-2-5-7 as my first job in the morning”. A standard oops interface includes a FILE/SAVE option along with standard Microsoft keys that are known to many users, and once trained in them apply to “all windows and web products” – not an exercise in teaching company defined keystrokes!

5. Standardization:
New technology standardizes the look and feel of your individual modules inside one (or just a few) programs, not only from the “windows look” but in the way that the business rules apply such as;
· Whether the company name of customers is labeled “Customer Name:” or “Client:” or “Name:”.
· Whether the company name of customers is “required”, or “capslock”, or “able to be changed by the user”.
· Whether the “Apply Finance Charges” option accepts only a Y/N value and whether the value for a new customer is defaulted to “Y” or not… and how!
· Whether one can delete a payment or not!
· Whether these kind of options must be re-coded for every module or not!

6. Combining Similar Functionality:
One of the most visible changes of a conversion to oops takes similar DOS executables such as “Enter Sales Order”, “Change Sales Order”, “Delete Sales Order”, etc. and moves them into one program. The ability to do this is the power of oops centralized coding and new windows technology which just simply outperforms DOS technology and spaghetti code.

7. Transaction Control:
One of the most basic data related improvements introduced into database technology since most DOS programs were written is transaction control, where “half baked” transactions that partially succeed, leaving a cleanup job for IT are totally eliminated.

8. Speed:
It is true that DOS speed is unmatched by windows technology. It’s not true that this is a significant advantage considering that the reason for dos speed is partially that the transactions do not flow thru centralized business rules to perform their database actions, but simply “write to disk” directly!

9. Maintenance:
Once your system is retrofitted to use oops programming style and structure, changing a business rule such as the way a sales order is calculated is a matter of changing the business layer rule in one spot, instead of updating “sales order entry”, “change sales orders”, “print unshipped orders”, and “update order as delivered”. The tongue in cheek saying for this amazing new technology is; “One changes the business rule in just one spot, and the resulting code is either perfect system wide, or wrong system wide!”.

10. Investing in Technology:
The time to invest in a DOS to windows conversion is overdue. If you’ve waited for the “wrinkles to smooth”, the “bugs to be fixed”, or determined in the past that the “investment” wasn’t worth the result, then I believe you are on the brink of extinction, because the software engineers that understand BOTH the dos and windows technology (and hence the ability to render a modern version from the old true code) are on the verge of retirement! If you wait, it’s a total rewrite to face.

Summary:
These are my top ten reasons to consider a DOS to Windows conversion, and if you started with a goal to port some of your functionality to the web, please consider the windows conversion a half-step there, because most platforms/languages have an extension of the business rule layer that is applicable to the web, or usable by a webapp so that part of your cost is a move closer to internet presence, whether it be customer data sharing, order entry, part availability, or simply customer and prospect information gathering.

About the Author:
By: Peter A Donovan
Applause Software of Boston, USA http://www.applausesoftware.com/
Member in good standing of the NEDC Programming Group: http://www.nedataflex.com/

Peter started his IT career as a combined sales executive/custom application developer the year following the release of the IBM PC. After similar corporate positions, where he was responsible for both Sales and Programming responsibilities, he obtained a position with a software distributor/authorized factory technical service center, where he excelled in custom application development for many different industrial and commercial markets and also travelled throughout the USA, Canada, Europe, and Africa training IT staffs in correct implementation of OOPS foundation coding technology and data dictionary technology.
Currently an independent IT consultant specializing in database software, Peter is actively involved in bidding on new challenges, maintaining a customer base, and publishing a freeware database contact manager “rolodex style” called RoloFLEX as a showpiece for his business.
www.RoloFlex.Biz

Visual DataFlex Class~ Instruction via Internet

2008-07-24T03:34:00.000-04:00

Internet Or In-Person Instruction In Visual DataFlex:
*Highly Competitive with Data Access Rates!

"The wide open possiblities of coding techniques can be explained in conceptual terms so that you code to form a solid foundation for your application based on correct OOPS programming concepts."

Internet Instruction Benefits:
"a 10-20 hour course @ $80 per hour using your application will cover all of the topics of a classroom environment without the travel, hotel, and inconvenience and produce usable and functional code for you to implement at your company and use as a reference".

"GoToMyPC, PCAnywhere, VNC, or other communication software puts us on the same desktop together, while we discuss the challenges you are facing and decide upon the most useful tools available to use, and the best OOPS techniques to use to accomplish your goal."

Global Internet Instruction:
Applause Software can offer voiceover communication while we codevelop your application thru instruction: please see: http://www.skype.com/ which allows free communication from Applause to you with the use of a headset with microphone.

Kindly reach Peter A Donovan at http://www.applausesoftware.com/ for further details!

Container Technology in Visual DataFlex

2008-07-24T03:03:00.000-04:00

Recently, I worked with a co-developer who coded a similar procedure such as this:

Procedure Item_Change integer iFromItem integer iToItem returns integer

Integer iRetVal
Forward Get Msg_Item_Change iFromItem iToItem to iRetVal

If (Current_Col(Self) = 2) Begin
Send Request_Save of oProdLine_DD
End
Procedure_Return iRetVal
End_Procedure

What came of the conversation we had was that the "Send Request_Save" actually (and unintentionally) avoided the container technology of Visual DataFlex so that validation, the confirm message, and the ability to augment these functions in the container were completely misdirected!

Here's what happens when a Request_Save is sent by normal means (i.e. clicking the save button, using the save key, changing a row in a dbgrid, etc):

The container runs request_validate of the server ddo and validates the datadictionary class rules upon the data. Upon failing, the save is aborted, a message about the error is sent to the user, and the focus attempts to go directly to the window or cell that doesn't pass validation. Upon success, the next step occurs.
The container then runs the function named in the verify_save_msg property handle. "Would you like to save?", or a custom message if you have programmed it. Upon a NO answer, the save is aborted and the focus returns to the object or cell in the focus tree. Upon a YES answer, the save cascade of messages continues.
The container then asks the DDO (server) to save. Upon any error, all changes are rolled back and the focus returns to the object/cell in the focus tree.
Then, the container (if it's not a data aware grid or list) clears the buffer and the ddo record attached to it.
Then, the container (if it's not a data aware grid or list) sends the message "beginning_of_panel" (augmentable) which determines the first focusable object on the form/view and gives the focus to it.
DONE

So, as many are aware, when you take control of the save mechanism to do it manually, you should do the following steps:

Request the ddo validation to a boolean: Get Request_Validate of oProdLine_DD to bCancel.
Ask or confirm the save: Get Confirm "Would you like to save?" to bCancel
Send the save command: Send Request_Save of oProdLine_DD
Upon success, clear the record: If (Not(Err)) Send Clear of oProdLine_DD
Move the focus: Send Beginning_Of_Panel

So, in summary, the container technology has 5 main steps to it (actually six!). Prior to any of the five actions, it asks the server DDO if there are any changes to save! If there are no changes to save, then none of the above five steps ever execute.

Many are familiar with the Save cascade of messages from creating, backout, update, etc. but the container cascade of messages/methods is also important to realize prior to the save cascade ever occuring.

Posted by:

Peter A Donovan

http://www.applausesoftware.com/

Uniform Rental Service Employee Paid No Contract

2008-05-15T04:45:00.000-04:00

What you need to know about Employee Paid and Negotiated Uniform Rental Programs.

The author Peter A Donovan is not affiliated with any unform rental company now, and was previously employed in the industry for 12 years negotiating rental contracts and speaks from this experience.

For the sake of mathematics, let's assume the ABC Manufacturing Company has 10 employees who pay and contract for uniform rental service, and that ABC will not payroll deduct or manage uniform service for unnamed reasons which could include overhead of management time.

What impact does this have on quality of uniforms, price, and the selection of a uniform rental firm?

To understand, you need to be "in the head" of a uniform rental company.
In a normal situation, where ABC negotiates and signs a contract, here's what happens. The uniform rental plant bidding for the business does this:
Each employee gets an inventory of 11 uniforms: 5 in the locker for M-F, 5 dirty in the plant being cleaned from last week, and 1 on the back of the employee, a "swing" garment.
Uniforms cost money. Let's just say each uniform outfit costs $75, and with 11 to purchase, that comes to $825 - not a trivial amount. They "lay it on the line" with a 3 or 5 year contract at $14.00 per week coming in per employee and give new garments to begin service. Math please! That comes to an income of 14x52 weeks = $728 per year. There is cleaning, employees to pay, trucks to maintain, and gas prices too. The normal new uniform contract takes about 1/2 the contract amount to break even. Let's not even go to "value of money over time". The uniform rental plant is in the business of long term profit and when you renew your contract for another 3 years, there's no huge overhead so there is finally some profit at the end of the tunnel.

Now, when ABC refuses to sign a contract (employees cannot) what does this do?
You have to be the uniform company on this one.
First, let's talk about the "stock room" of uniform rental plants. Every plant has a stock room full of used garments that they decide are good enough to rent but used, so they use them a replacement garments when regular uniforms are destroyed and for employees added to a contract during the contract period. When you have a sizeable stock room bulging with used uniforms, you can go after employee paid no contract accounts. $14 per week per employee still and used uniforms. Wait.

Who has uniform stock rooms bulging? When a uniform company has customers that end contracts, all the uniforms are returned to them. When a uniform company has a low quality control standard for used garments and retains all rather than RAN "replace as needed" you get the perfect mix.

If your customers are happy and don't leave, PLUS you have a high quality RAN system, you just can't bid for the ABC account, can you?

So, the impact of ABC's non-involvement does this:
1. The uniform vendor will be of the type mentioned above most likely.
2. The employees get used and pay for new.
3. AND they impact the image of the ABC company when visitors arrive.

This article is written expressly for reading by the owner of ABC, whomever you may be.

Sincerely,
Peter A Donovan
Applause Software
http://www.applausesoftware.com/

Uniform & Linen Rental Plant Software Launched

2008-05-05T17:06:00.000-04:00

A new software product for commercial textile rental plants (uniform & linen rental) will be launched this week from Applause Software of Boston.

Created in 20066, coming to market now, is RoloFlex UL.

A Sales and Marketing contact manager featuring custom proposal generator, email blaster, document management and scanning, market share analysis, targeted lead generation, and salesrep activity monitor, RoloFlex UL will be launched this week with a nationwide telemarketing campaign.

Based on a Visual DataFlex front-end, this product is years in the making and is singly the only PRO application available for the industry specifically.

There are approximately 400 commercial textile plants in the USA specializing in uniform rental and linen rental. The organization that forms the association for these companies is the Uniform Textile Service Association (UTSA) which features a publication and trade shows for the industry.

RoloFlex UL is currently featured on: http://www.roloflex.net/

Author: Applause Software of Boston: Peter A Donovan http://www.applausesoftware.com/

Microsoft TAPI DIALER with Vista

2008-04-13T06:55:00.000-04:00

With the advent of many new things in the Vista OS, there is an important undocumented method for using an application which utilizes the TAPI (Telephone) interface to Vista.

In a microsoft support conversation I had with the MS support team, I suggested the following:

Bug: The MS-Dialer in Vista is not backwards compatible with XP.

Bug: There is no documentation in Vista on how to use TAPI or the MS Dialer.Exe

Bug: The documentation that MS provided does not dial USA phone numbers correctly.

Here's the problem:

If you were to dial in XP, you would dial this: 1 781 555 5555 as an example. This no longer works in Vista, and the output dialed is exactly this: 1 7 555 5555 where 2 digits of the area code is truncated.

If you were to follow the (paid to provide) documentation, you would now dial: +1 781 555 5555 but this results in the following number dialed: 781 555 5555 without the long distance "1".

The Answer:

Short and sweet: You must take the digits previously dialed by XP and add the country code for the USA like this: "+1 17815555555" with an important space after the "+1 ", resulting in the number dialed of 1 781 555 5555

This will be an important new addition to programs (such as RoloFlex from http://www.roloflex.biz/) which perform under both operating systems, XP and Vista, so the programmer must identify the OS and adjust the TAPI interface accordingly.

In the hopes of helping someone else with their TAPI interface, so that you don't have to pay Microsoft $59 US to help you discover this....

Regards,

Peter A Donovan : Applause Software, Boston USA http://www.applausesoftware.com/

EMail Marketing with Visual DataFlex Software

2008-03-15T03:19:00.000-04:00

An amazing return on investment can be obtained from email marketing to your customer and/or prospect base...

... considering [as example] the “under $1,000” customized package available from Auto-Mate Software from longtime VB and VDF developer Garret Mott of the NEDC.

Once installed, you can instantly notify your entire market that new products are available, or write pre-written excellently worded letters that are sent to individuals when the need arises.

Layman’s terminology only:
1. Write an email. Edit carefully, proof, and save into a database using a windows program that guides you.
2. Select whom out of your database you’d like to send it to.
3. Click a button, and each of your prospects receives an individual email within minutes.

How to slice and dice your market:
Let’s assume you have a database with customers and prospects. If you don’t, it’s time to take this on. Your database contains vital information about each entry such as the zip code, state, type of account, balance, payment terms, etc.
What if you could instantly generate revenue for no cost? Let’s setup your email screen as Garret Mott would do for you. Select from a drop-down list “COD”, select “MA” (Massachusetts) and pick customers only. Write up an email offering 10% discount on orders in the next 48 hours, and send. When you feature a new product or listing on your website, why not let everyone know in a short email note?
The other use for this kind of tool is to respond to inquiries with pre-written letters, edited for presentation quality, available to send to individuals upon request of information. Each business model has a set number of popular inquiry topics that customers ask for. Currently, do you respond with ad-hoc written emails and mailing of literature? A pre-written letter send to the individual who requested the information actually takes less time and both makes a better presentation and offers a delivery vehicle to attach a .PDF document. No cost, improved results, and instant delivery.

These are the two most common uses for email marketing, but I’m sure you can think of more.

Delivery:
Are we all tired of the HTML emails that feature graphical art advertisements? The systems that I currently use feature plain text with links. They look like an individually typed email, and they are really. Many email recipients have “html off” as an option on their emails, so why send an email that only a portion of your readers will actually see?

Difficulties:
Many ISP’s (Internet Service Providers) have limits on how many emails you can send in an hour. We have found that options on your email sending package can spread these emails over the course of a day or two, or that simple negotiation with your ISP can unlock this limit. Many times a requirement that you include an “unsubscribe” link could be encountered, and is a good practice to include.
Summary:
Generate income, keep in touch with your market, break news instantly, and respond more professionally to both sales and service opportunities.

Recognizements:
Auto-Mate Software: http://www.automatesoftware.com/

Author:

Peter A Donovan, Applause Software: http://www.applausesoftware.com/

INCORRECT: Reports Of Visual DataFlex Corruption with Vista Home Edition: Read More!

2008-02-22T12:52:00.000-05:00

Recently, Many blogs are picking up a report from a single source which is reporting that various software packages running under Vista Home editions experience corruption: NOT PROVEN.

This was my response to the earliest and most reputable blog I found with the post:
I am posting it here in case they decide to block my reply:

I am the owner/lead programmer of Applause Software in Boston, a Visual DataFlex business solutions firm, and I have a google watch on Visual DataFlex…

I would like to ask for details on your listing of Visual DataFlex in this list.It is unlikely that a Visual DataFlex application would cause data corruption in this environment, but it is very likely, that because programs written prior to the UAC of Vista came to being, that a VDF program trying to access a registry value could produce error messages that would be mistaken for corruption.

In addition, users of Visual DataFlex are not aware of the exact backend database used for their application since it could be one of many including Oracle, DataFlex embedded database, Pervasive, MS-SQL, or other backend.

I would like to offer my services to get to the heart of this matter and as a professional developer in the language for 25+ years I would like to challenge this information at the source and ask for a consultation with the firm reporting this information please.

Until then, please to anyone watching this thread with VDF kindly consult your system IT professional for more informative information prior to canning your application!

PS: Always make a backup! Don’t wait for a reason!

Thanks,Peter A Donovan
Applause Software of Boston
[ a google will find me ]

Definition: Data Dictionary

2008-02-18T06:11:00.000-05:00

A data dictionary is defined as the business layer in-bewteen your table on disk, and the requested operation at runtime.

It handles the find, clear, save, validate, and delete requests from either the programmer or the user. A data dictionary exists both as a class coded definition and as an instantiated object which uses full delegation and polymorphism in the form of a data dictionary object in a "tree" structure for the data set you wish to perform an operation on.

Editing a DataDictionary CLASS in Visual DataFlex involves at least 10 identifiable options:

-1. Create/edit/delete data table columns.
-2. Set parent relationships.
-3. Define indexes for finding data by.
-4. Set column based options for when the data table is used as the main data entry source. This involves setting system-wide standard behavior such as "capslock", "required", and "auto-find". An option also exists to set columns as "key fields" where the user may not change the value at runtime.
-5. Set column based options for when the data table is used as a "server" [parent] of the main data entry source. Options here include "find required" and "noput" [user changes cannot overwrite the data table column]. It should be noted that depending on which place in the data operation structure (parent, child or main file... a data dictionary exists, the place determines which business rules apply in a display of polymorphism which is defined as the ability to produce different behavior simply by the context of it's use.
-6. Define the immediate relational tree for the delete operation based on a record delete in the table. The child tables are defined so that two basic rules apply (one or the other): either the record cannot be deleted if child records exist, or the child files will all be deleted when the record is called for delete AND a data dictionary object in the module must be present to handle the delete operation. This is as much a validation for the programmer as it is for the user, since operations cannot be successful unless both follow the rules programmed in the class. It should be noted that business rule exceptions and customized rules can augment this programming or replace it completely. It should also be noted that when data dictionary objects are connected together in a module, that deletes travel downwards in the tree, and upon each delete, a save and validation is sent upwards in the tree.
-7. Define the immediate relationsl tree for the save operations based on a requested save of the data table record. The parent data tables are defined so that your programming team must always place a parent DDO (data dictionary object - instantiated on the classes we are building) for each parent data table that is connected relationally. Omissions and "sometimes required" parent tables can be defined in both the class code and object code programmaticallty. The advantage of making a parent table "required" is to be able to both code update/backout operations to another table (knowing that it must always be present to handle your code), and also for the Visual DataFlex Studio to automatically model your relational tree when you request a data server to handle your find, clear, save, validation, and delete operations.
-8. Define the externally updated tables to be bound in the transaction block of saves/deletes. When a save or delete occurs, all table attributes are set to readonly momentarily, the tables that will be affected by the operation are set to default mode, and then a reread/transaction block occurs to lock all the tables in the tree that are affected PLUS the ones listed in externally updated tables. This allows, for instance, a reread and update from the system table to assign the next available number to a key field.
-9. Programming of stored procedures that exist as called methods already. REF: DDO Save Cascade: http://applausesoftware.blogspot.com/2008/02/visual-dataflex-ddo-stored-procedure.html
10. Programming of customized stored procedure methods that you introduce to the class, stored in a central depository (the foundation of oops programming) class and can be attached to either the exiting of a control attached to a column of the data table, or the exiting, or simply the validation of such column.

All together, these 10 functional abilities to centrally define data table rules are dwarfed by the fact that they are "hitched up in tandem" like a team of "Budweiser Clydesdales" which work interconnectedly to enforce your entire data structure on any data operation which includes save, clear, find, delete, and validation.

Find this definition and more at: http://www.vdfwiki.com/

By: Peter Donovan, Applause Software, http://www.applausesoftware.com/

Visual DataFlex DDO Stored Procedure Delegation

2008-02-05T22:32:00.000-05:00

As advertised: for Visual DataFlex programmers.

This is a snippet showing the Visual DataFlex cascade of messages that is called in each one of the data dictionary objects in a connected tree of data table dictionary objects in a form/view.

Creating: [a method to put code for new records only]
Backout: [a method to put code where the record on disk is in memory before ui]
Update: [a method to put code for all saves both new and existing]
Validate_Save: [a method to put complex validation or validation to be done after update]
Save_Main_File: [a method where the parent values drop down into the child and the record is saved to disk]

[ double click image to expand]

Regards,
Peter A Donovan
http://www.applausesoftware.com/

Oops foundation centralized coding in Visual DataFlex

2008-01-16T03:50:00.000-05:00

OOPS Foundation Centralized Coding in Visual DataFlex:

One of the most fundamental concepts in oops programming [object oriented] is centralized coding so that unlike previous spaghetti code where the same calculation was formulated over and over again in different code segments, instead we now place the code in one spot so that if business rules change then we go to one spot, change the code, and we're done.

Earlier attempts at centralized coding involved gosubs where the same piece of code was reused, but with Visual DataFlex, utilizing datadictionaries, we have hooks in the finding process and constrain process for instance where the code is placed in a "stored procedure" along with all the other rules of the datadictionary class for a table. In Visual DataFlex methodology, which supports full message delegation, the find passes through a DDO [data dictionary object] which delegates the find to it's DD class code and utilizes the onconstrain method of the class as well as the object.

Technique: in order to fully utilize delegation, we "forward send" each message even if it is an "event" method.

The code described below takes a business rule exception to constrain a table by it's status which is used throughout a system in many places including windows data entry, batch processing, and webapp interfaces.

The beauty of Visual DataFlex database centric code is that this one event can be turned on or off by a property setting [business rule exception] in any of the above mentioned applications.

Here's some sample code:

This is intended as a "get-to-know features of Visual DataFlex" article.

Sincerely,

Peter Donovan

The NorthEast DataFlex Consortium

2008-01-15T06:06:00.000-05:00

The NEDC: what it is!

The NEDC was formed in April of 2003 by a group of New England based Visual DataFlex custom application developers with varied specialties. It offers "the power of a large corporation without the large cost" for potential software partners/clients and is noteworthy as being the largest single resource for Visual DataFlex programming in the United States.

Why Choose the NEDC?
The NEDC is a group of independent Visual DataFlex (VDF) programmers that have joined in camaraderie to provide increased value and capabilities to their customers. The NEDC is not a conventional consulting firm, or even a legal entity, but “an almost virtual company”.
We think this concept works to make the NEDC an exceptional partner for your business, as we can offer the power of a large corporation without the cost.

· Experience: Collectively, the NEDC provides over 150 years of VDF (and other language) system development experience. Whether your needs are for an inventory, sales, manufacturing, time & attendance, ERP, or some other kind of system, we most likely have real life experience implementing similar systems.

· Skills: When working on a project, the person best suited to a particular portion is the one doing the work. NEDC members have worked in many environments: independent, small business, corporate and as a VDF instructor. This gives us real life understanding of how companies work. We all started in character mode (DOS based) DataFlex, so we know the language from the ground up. Most of us are also involved in testing of the newest version, so we know what’s coming.

· Project Types: We work in many different ways: conversions of character mode DataFlex systems to VDF, conversions of systems written in another language, maintenance of existing VDF systems, and whole new systems. Whether you need a classic Windows system, a Web-based system or a combination of the two, we can do it.

· Costs: Being a “virtual company” saves our clients money: no rent, tax burden or administrative costs to pass on. This means that we can work for a substantially lower hourly rate while providing excellent service. Of course it also means we can’t invite you to visit our expensive corporate headquarters! Instead, we come to you, which helps us get a better picture of how your company works.

· FLEXibility: The NEDC normally assigns one developer as project leader. If he goes on vacation or gets sick, another fills in. If you prefer to work with another developer as lead, simply ask and we’ll swap roles. This means that you are in the driver’s seat, not at the mercy of someone you’ve never met deciding that another project is “more important” than yours or that you will have to work with a particular person.

· Security: If you are used to working with a single developer you may worry about something happening to that person. In the NEDC, if something were to happen, another developer will switch into the role.

by:
Peter A Donovan
Charter Member of the NEDC (NorthEast DataFlex Consortium)

RoloFlex Release: Press Release and Marketing

2007-11-12T03:03:00.000-05:00

RoloFlex 12.5 Released November 2007
Featuring Visual DataFlex

Rated highly by submission to download sites listed herein, the RoloFlex CRM/PIM [customer relations management/personal information manager] is going out to major download sites and features the upgraded RoloFlex product released with the Visual DataFlex 12.1 platform.

The marketing effort for RoloFlex is just beginning!

Soon, RoloFlex will be available at most major download sites featuring anonymous download under the Visual DataFlex 12.1 evaluation period and subsequent registration/licensing when registered through http://www.roloflex.biz/

Under Construction: RoloFlex Time Tracker 12.5 for billing hours and invoicing.

Nearing Release Now: RoloFlex EMail Module, due for distribution on November 15 2007

Please Note the RoloFlex Blog Site http://www.roloflex.blogspot.com/ for future news!

Sincerely, Peter and Kimberly Donovan

DDO Tree Technology – DAF Methodology

2007-10-09T19:08:00.000-04:00

Terms:
DDO Tree: A combination of instantiated data dictionary objects tied together.
DAF Methodology: How the ddo tree handles find, clear, save, delete and validation.

Here’s a sample (simple) ddo tree as found in a sales order data entry program or other module…

“Knowing how the ddo tree handles user requests is at least important to know as how to model a data dictionary class”

Communication between the ddo tree and the objects in play is a two way street!

In this example of data entry, the Server of the main panel is Salehead and it controls the find/clear/save/delete and validation of itself and all it’s parent ddo objects.

In a lesson in polymorphism, the “Customer” ddo recognizes it is a parent object of the server in play, and enforces different rules (find required on record for instance) than it normally would if it was the server itself.

Further, the SaleHead ddo takes responsibility for accepting the find/clear/save/delete messages sent via the user. When the cursor/focus is in the customer name window, for instance, the request_find message actually goes directly to the SaleHead ddo, not the Customer ddo. The SaleHead realizes that the message is directed at a parent ddo and forwards the message up thru the connection to the Customer ddo to handle.

Test!
Take your data entry module with parents and put a hook message inside the server and the parent “request_find” method and see which pops up first!

In the same way that this communicates upwards, it also communicates downwards so that when a delete message comes to the server, it travels downwards, deleting all children of the server and then itself. The beauty of the methodology is that no parent records can be deleted by the user unless programmatically allowed by the software engineer.

Test!
Take any data entry module, place the focus in a parent object cell or window, and press delete. What get’s deleted? Not the parent!

So, augmentation of ALL find/clear/save/delete requests can be done at the server level! Here’s how to code so the customer of an order cannot be changed:

Object Customer_DD is a Customer_DataDictionary
End_Object

Object SaleHead_DD is a SaleHead_DataDictionary
Set ddo_server to Customer_DD

Procedure Request_Find Integer iMode Integer iFile Integer iIndex
If ((iFile = Customer.File_Number) and (Current_Record(Self))) Procedure_Return
Forward Send Request_Find iMode iFile iIndex
End_Procedure

Procedure FindByRowID Integer iFile RowID riRowID
If ((iFile = Customer.File_Number) and (Current_Record(Self))) Procedure_Return
Forward Send FindByRowID iFile riRowID
End_Procedure

End_Object

Test!
This is one correct way to code a sales order so the parent cannot be changed of an existing sales order!

So, what have we learned? DAF Methodology.
It’s a study of communication between data entry objects which delegate user messages to the server, and how that server communicates the messages to it’s parent and child tables.

Visual DataFlex DDO Tree Technology Reference

2007-10-03T08:31:00.000-04:00

A Reference Guide of DDO Technology
– Visual DataFlex–

Outline Mode:
- Introduction
- Terms
- What is a DDO?
- What is a DD Class?
- What is a DDO Tree?

Introduction:
Based on DAF Methodology, the DDO Technology in Visual DataFlex is a study of instantiation, delegation, and polymorphism.

Terms:
Instantiation: The act of creating an object based on a class and class hierarchy.
Delegation: Visual DataFlex features natural full delegation of methods by default, where the method travels first to the object, then to it’s superclass, and on throughout the full class hierarchy until the method is resolved. A method runs to completion without augmentation or definition on the object level but such augmentation, forwarding, or canceling is supported on both the class and object level.
Polymorphism: The act of an object to produce different behavior depending on it’s context.

What is a DDO?
“data dictionary objects” are instantiated in each data entry (or other type) module for the purpose of:
- Providing a “server” for find/clear/save/delete and validation operations for a data table.
- Providing data aware controls with attributes such as capslock, valid values, default values, range definition, selection list definition, etc.
- Communicating with other DDO’s in tandem to do all of the above with coordination.
- Definition of “constraint data filters” where your data can be a subset of the whole.

Sample Object Code:
// doc: instantiation of customer_datadictionary class placed inside panel of data entry form.

Object oCustomer_DD is a Customer_DataDictionary // instantiation of class.
Set DDO_Server to oSalesRep_DD // parent or “server” ddo
Set DDO_Server to oTerms_DD // parent or “server” ddo
Procedure OnConstrain // predefined method
Forward Send OnConstrain // continue delegation
Constrain Customer.Active EQ “Y”
Constrain Customer As (Customer.TotalOwed What is a DD Class?
A data dictionary class is a number of things: about 10 major functions with more omitted for space constraints in this article.

[1] A Data Dictionary Class defines the attributes for the data table to be communicated to the data aware controls tied into that database table. Attributes include “capslock”, “required entry in this column”, “auto-find upon exit”, “shadowed/non-enterable”, etc.

[2] The DD Class sets the (above noted) attributes differently depending on whether the ddo (instantiated object based on the class) is the direct server of operations, or a parent ddo of the operations server. This creates polymorphism on the object level and allows parent records to be found, required to be found, but not allow changes, for instance.

[3] The DD Class defines which other database table objects must be instantiated alongside with it to perform save and delete operations. For instance, the save of a sales order lineitem would require a dd object (ddo) for the product it was related to in order to reduce inventory or create a backorder. In another instance, the sales order header would require a ddo for the sales order lineitem to be present in order to delete the related order lineitems. Also, a DD Class may be configured to not allow deletes if child records exist.

[4] The DD Class allows columns to be associated with a “selection list” or lookup object. The chosen selection list will create a lookup button on the control chosen for that column and automatically popup and communicate two ways with the selection list.

[5] The DD Class allows the database programmer to define the object labels for each column and also to default the creation of controls for this column to a certain type such as a spinform or comboform, etc. (communication with the visual dataflex studio).

[6] The DD Class features augmentable save, find, clear, delete, and validate methods. The operations server (ddo) in a form or “view” will initiate a cascade of messages designed to perform an operation such as a save operation. When this save occurs, it cascades to all the connected data dictionary objects in the form or “view” which then delegates to the DD Class where you can augment the operation based on business rules you define and business rule exceptions which can be controlled via various means, usually with a property setting.

[7] The DD Class allows the setting of “valid values” validation tables which accompany a column in whatever control form it takes (regular form, comboform, or in a grid). The DD Class can define a list such as “activeinactive” for itself, or share a validation table with other DD Classes such as a list of US states or valid shipping terms.

[8] The DD Class allows for the definition of entry and exit methods for each column of the database table. Whether the column, in data entry, is represented in a comboform, or in a grid, the entry and exit methods follow it.

[9] The DD Class allows for auto-incrementing from a “system file” for ID fields, for instance or lineitem numbers.

[10] The DD Class communicates when instantiated, to validate the find/clear/save/delete cascade of messages along with whatever other ddo objects it is connected to.

What is a DDO Tree?
Data Dictionary Objects are run in tandem to find/clear/save/delete and validate these operations.
Let’s take a sales order entry application for example. The business rules given to you are;
· Customers who are not active may not purchase.
· Active customers may not go over their credit limit by more than 10%.
· Sales orders update the customer total owed.
· Lineitems update both the sales order total and reduce product from inventory.
· Product records update vendor purchase history.
· Sales orders update the salesrep volume sold.

Here’s a sales order entry application ddo tree (simplistic) example:
// doc: ddo tree for SO application
Object oTerms_DD is a Terms_DataDictionary
End_Object

Object oSalesRep_DD
End_Object

Object oCustomer_DD is a Customer_DataDictionary
Set DDO_Server to oSalesRep_DD
Set DDO_Server to oTerms_DD
Procedure OnConstrain
Forward Send OnConstrain
Constrain Customer.Active EQ “Y”
End_Procedure
Function Validate_Save Returns Integer
Integer iReturnVal
Forward Get Validate_Save to iReturnVal
If (Customer.Owed > (Customer.CreditLimit * 1.10)) Error 999 “Customer Over Credit Limit”
Function_Return iReturnVal
End_Function
End_Object

Object oVendor_DD is a Vendor_DataDictionary
End_Object

Object oProduct_DD is a Product_DataDictionary
Set DDO_Server to oVendor_DD
Procedure Update
Forward Send Update
Add (Product.Qty * Product.Price) to Vendor.Volume
End_Procedure
Procedure Backout
Forward Send Backout
Subtract (Product.Qty * Product.Price) from Vendor.Volume
End_Procedure
End_Object

Object oSaleHead is a SaleHead_DataDictionary
Set DDO_Server to oCustomerDD
Procedure Update
Forward Send Update
Add SaleHead.Total to Customer.Owed
Add SaleHead.Total to SalesRep.Volume
End_Procedure
Procedure Backout
Forward Send Backout
Subtract SaleHead.Total from Customer.Owed
Subtract SaleHead.Total from SalesRep.Volume
End_Procedure
End_Object

Object oLineItem_DD is a LineItem_DataDictionary
Set DDO_Server to oSaleHead_DD
Set DDO_Server to oProduct_DD
Procedure Update
Forward Send Update
Add LineItem.Total to SaleHead.Total
Subtract LineItem.Qty from Product.QtyOnHand
End_Procedure
Procedure Backout
Forward Send Backout
Subtract LineItem.Total from SaleHead.Total
Add LineItem.Qty to Product.QtyOnHand
End_Procedure
End_Object
// END CODE

With a pictorial version of what’s happening in the tree:

RoloFlex Companion #1

2007-09-27T04:28:00.000-04:00

The first RoloFlex Companion Product *for Professional Version Only will be Launched on November 15th.

Contributed by longstanding custom app developer Garret Mott of Auto-Mate Software.

Note: Garret has done a number of custom email managers, adding in features such as disclaimer, logo as an image, signature with custom field placement capability, attachments, well... it has a lot of features. Any developer looking for a custom email attachment to their product please contact http://www.automatesoftware.com/.

Note: This is intended as a launch of companion products, both for RoloFlex, and a platform for getting your Visual DataFlex product out in a new market. Please contact http://www.applausesoftware.com/ for more details and a prototype agreement.

Thanks! Good luck to the pooch - "Rolo".

www.RoloFlex.Biz - New Home for RoloFlex

2007-09-22T05:17:00.000-04:00

RoloFlex: now 2 flavors:

Personal and Professional

*The professional version simply has a valid VDF client license sold for commercial/business clients.

The new home is:

http://www.roloflex.biz/

And a more professional interface is coded to accomodate the release.

Regards, Peter & Kimberly Donovan

A guide to discovering the Visual DataFlex Studio

2007-09-21T10:39:00.000-04:00

A beginner’s guide to coding a custom database application in *Visual DataFlex
by Peter A Donovan/Applause Software/Boston.

*Visual DataFlex is a trademark of Data Access Worldwide of Miami.

Overview:
Here’s a conceptual step-by-step methodology for creating your first Visual DataFlex application.
Note:
Visual DataFlex is a “transparent back end” database application studio where the same exact code runs on your choice of backend.
This overview assumes you will start with the native DataFlex backend as a starting point.
Goal:
To encourage you to try the Visual DataFlex studio for a test drive using [freeware] the Personal DataFlex edition licensed for personal but not commercial use.
This is a full studio deploy with no restrictions other than mentioned above.
Compelling Reasons:
You can most likely produce a fundamentally solid application in ½ the time as your current studio.

First, let’s assume you have the studio downloaded from http://www.visualdataflex.com/ and you are running on a 30 day eval prior to getting a license.

If you fire up the Visual DataFlex Studio, you’ve got the “order entry” sample example workspace automatically loaded for you, and the current project is “Order.src”. From this point, you should hit [F5] and the “source code = src” will compile into an executable and run. Please check out the features of the running program. This, we will code ourselves in a new “SRC” project to see how it was done.

1. From the menu, choose File-New-Project-Windows Project, and you will get a dialog asking for the .EXE name. Please type “Test” and press ok.
2. For fun, just hit [F5] and compile an executable, which you will find is a perfect MDI [multiple dialog interface] container with no functionality BUT… the button bar, menu headers, and runtime are all done.
3. Back in the Studio, let’s create a data entry program or form if you will. Click File-New-View/Report-Data Entry View Wizard, and click Ok.
4. From the wizard, click “next” on the opening page.
5. For an object name, please enter “oSalesOrder” and accept the defaults for the next 2 windows and click “next”.
6. Next page: change the radio button please to select “create a header-detail entry view” and click “next”.
7. Now, the time has come to select the CHILD table for the data entry view, so highlight “OrderDtl” and click “next”.
8. For the “header” data table, we will select “Orderhea” and click “next”.
9. Now, we select the columns “fields” to show in the data entry HEADER section, and I recommend: Choose ALL the columns from the OrderHeader table EXCEPT the last one [last detail number] and click “next”.
10. Now, we select the columns “fields” to show in the child grid below the header, and I recommend: Choose ALL the columns [except for the FIRST : ordernumber] from the detail table and click “next”.
11. Next, you get to customize the labels for each of the forms if you like, but the default has already been programmed into the datadictionary, so simply change the radio button to “right” justify the labels, and click “next”, and “Finish”.
12. Press [F5] which auto-saves and compiles your SRC into a EXE and test!

You now have a running program [under the view menu] which actually saves sales orders and detail lines. Not the most appealing visually, but structurally sound.
You will find that there are entry methods associated with some database columns, and exit methods associated with some. You MUST find a parent table record in order to save, and you MUST fill in some required fields. There’s a snazzy lookup list [expandable] for each of the associated tables, and some columns automatically are instantiated as comboforms for you automatically. A couple of small modifications later and we are on the road to deploying this. [omitted].

This is just a sample of the power of Visual DataFlex, and a few words of explanation are required to answer questions that this may have raised.

* The datadictionary for each of the tables has been pre-coded for you in this sample example.
* The datadictionary for the parent tables adjusts automatically, knowing that it is used as a parent reference, to be “find required” in an excellent display of polymorphism. The same exact table behaves differently when it is the main table for data entry, i.e. no “find required”.
* The key fields/columns of each table cannot be changed: they are protected from change via a checkbox in the datadictionary.
* The labels for each column are configured in the datadictionary so they appear consistent throughout your application.
* The lookup lists, called selection lists are assigned to a table-column in the datadictionary so they automatically appear with a prompt button with no code.
* The Order Header TOTAL automatically adds and subtracts based on what you do with the lineitems: delete/save new/change.
* The Product on_hand total automatically adds and subtracts based on what you do with the lineitems: delete/save new/change.
* For a real LASTING impression of visual dataflex, please note the quantity onhand of a lineitem product, and then CHANGE the product in the lineitem without changing the quantity. * Then, choose the lookup, and you will see that the lineitem quantity has been moved back INTO inventory for the product you changed. Note: there are about 5 lines of code in the datadictionary that make this happen!
* Now, for real fun…, place the cursor in the header section on customer and choose DELETE from the button bar. Surprise, the customer is not deleted but the entire order and all of it’s lineitems are deleted. Repeat: place the cursor on the product code column of an existing lineitem and hit DELETE. The product is not deleted, but only the lineitem.

By this point, you may be ready to give the datadictionary a once-over!
From the Studio, select Tools-Database Builder. This utility creates the CLASS that each datadictionary object [in your entry form] is based on.
From the “Open Table” pulldown, select “Order Header” and browse thru the settings. It’s extremely impressive I think in the maturity of the product.

Ok, you want to give Visual DataFlex a shot, but where do you go for help?
The Visual DataFlex newsgroup: The url is: news://news.dataaccess.com/visual-dataflex
Please introduce yourself as a new developer and we will welcome you with advice and support.

Thanks for giving Visual DataFlex a trial, and look forward to seeing you on the newsgroup!

Sincerely,
Peter A Donovan
http://www.applausesoftware.com/ of Boston, USA

The Agile Manifesto

2007-09-21T05:35:00.000-04:00

Quick Note:

This morning, I read one of the greatest blog articles by Joe Coley of the NEDC. In a newly opened blog, Joe's article just posted features the AGILE MANIFESTO which is an incredibly poignant statement about software development philosophy.

I recommend checking in on Joe's blog as a "must read"- http://itknowledgeexchange.techtarget.com/customapps/

Joe's photo and background can also be found at:
http://www.nedataflex.com/NEDCtest1.asp?pageid=22

PS: You can become a signatory of this manifesto if you agree with it's content.

Publising an article about Visual DataFlex

2007-09-20T22:19:00.000-04:00

Publicity for Visual DataFlex:

I am writing this article specifically geared for Visual DataFlex developers who would like to write an article publicizing your views or information about visual dataflex...

I personally have tried to publicize VDF thru article writing, and posting to different sources, and would recommend the following strategy to anyone who would like to do the same:

In looking for publicity for Visual DataFlex and other associated products, I use this resource to locate a suitable article site:

http://www.manhattanservice.com/

Manhattan Service is a SEO optimization help site, but specifically a inner link especially for articles:

http://www.manhattanservice.com/network/article-directories/

which lists [at the bottom] a number of article sites which accept free articles.

Now, from experience, I recommend 2 sites from this list:

EZine

and

Buzzle

The compelling reasons I recommend these two sites are:

[1] Will my article be formatted nicely and not cluttered with advertisements on key words within my article?
[2] Will the page rank [power to make the article stand out on google] be high enough to effectively publicize my work?
[3] Are the site underwriting standards tough enough to eliminate spam articles so that my article will not be cluttered by junk articles, AND will it stand a chance of being distributed to other article sites?
[4] Will they review and approve my article in a reasonable time frame?

Sites to avoid:
ISnare - this site effectively only publicizes when you pay and your articles will just hang in limbo until you do.

Secondary Site:
Article Factory - this site has low underwiting standards and your post will disappear in time if not popular, however they feed other channels and my article on Visual DataFlex product review got over 600 views, 21 other sites picked up the article, and it is still up and running.

Note: If you have a blog, and feature articles about Visual DataFlex in the blog, I recommend you visit www.BlogUpper.Com [a child site of Manhattan Service] for assistance there.

If you have a topic to write about, and would like to further the cause of Visual DataFlex, please consider publishing an article or more thru these channels!

Sincerely,

Peter A Donovan

RoloFlex 12.4 Released Today

2007-09-17T17:06:00.000-04:00

RoloFlex 12.4 Released:

RoloFlex 12.4 was released today as a small upgrade to RoloFlex 12.3 which features finishing work to isolate 2 small bugs and add 4 small features.

Features Added:

Print List Of RoloFlex Entries
Print Envelope
Active Toolbar with more choices and data aware highlighting courtesy Peter Brooks [Australia] based on work by Vincent Oorsprong [Netherlands].
Color (or colour if you prefer) added to notes courtesy Nat St. Pierre [Canada].

Bugs Fixed:

[export all and re-import all did not function properly in all cases]

[print lead card was not programmed]

In addition, RoloFlex has been featured in some web articles, and is starting to be offered by some free software download sites:

http://www.freewarehome.com/index.html?http%3A//www.freewarehome.com/Business_and_Productivity/Business_Specific/Sales_t.html

and featured alongside the release of Visual DataFlex personal edition:

http://www.dataaccess.com/enews/2007/Jan_18_2007.htm

Thanks to all who contributed to this revision,

Regards,
Peter and Kimberly Donovan

Rewrite: VDF or VB? VDF Advantages

2007-09-10T00:51:00.000-04:00

Visual DataFlex Advantages

Ref: Should I rewrite my system in VB or VDF?

Visual DataFlex (VDF)

VDF’s main advantage is speed of development. On a system that deals with large quantities of data, VB will probably require twice the coding time.

One example of this is in error handling. In VB error handling must be coded by hand.

Another example of “out of the box advantages” is the find messages of VDF. Coding “find first or last” is completely supported and coded by VDF into augmentable methods available at both the object and datadictionary class levels.

Overview: VDF is designed for data awareness in a completely scripted environment while VB is not designed as a data aware out of the box solution.

Second, VDF is completely in harmony with your current code base and data.

A conversion of DOS DataFlex to VDF can take your tried and true code and move it mostly intact into an OOPS VDF system dependably without reinventing the wheel.

A conversion of DOS DataFlex to VDF also has the advantage of being run simultaneously with DOS. You can phase the system in gradually instead of being an all out conversion. You can even use the same data tables as DOS until the conversion is complete, and then switch over to client-server when VDF passes validation and takes over the complete role from DOS.

VDF is a great front end for many databases: DataFlex, Pervasive, MySQL, DB2, Oracle, and MS SQL Server for example. The same program code will work, no matter what database you choose (or switch to).

VDF has a 30-year history as a development language designed for working with data. VB has data capability as an add-on. The first 2 versions of VB weren’t even database aware!

VDF has a light footprint. Complex systems can run tolerably well on 5+ year old computers. VB.net requires “power-user” type computers for all users to get reasonable performance.

VDF is truly Object Oriented. This type of programming makes development faster, cleaner, & more easily changed down the road. VB is “Object Based” – a partway implementation of the OOPs concept. One part of OOPs is “Classes”. These allow flexible extension of the controls that are used to display data.

· For example, suppose you want to color all fields that are indexed (& therefore can be used for finding). Add the code for doing this into the class, recompile & now every instance of every field that is indexed will be colored. In VB, this change could take weeks – finding every control & adding the code to it.
· Another major advantage to this process is centralized coding. If, for instance, you wanted to change the color assigned to the indexed fields VDF can do this by changing one centralized spot, giving both great power to your code, and also making month-to-month maintenance chores a snap rather than a huge conversion job.

VDF has Data Dictionaries. DD’s are arguably the most powerful part of VDF. All business rules & much of the custom code go here.

· The advantage? As a very basic example, say you always want the Customer Name capitalized. Set this in the Customer DD. From then on, every view, dialog, etc. that uses the Customer DD will always capitalize the Customer Name.

· Two years later, you decide to allow lower case. Go to the DD, change it there & then recompile the application. Every place that uses the Customer Name (doesn’t matter if it’s 1 place or 100) will now allow lower case.

VDF’s Interconnected Data Dictionary Rule Base:

In a VDF application, the database table rules are coded [as above] with basic and advanced business rules. Example: The customer table has a globally applied rule that says the customer can’t go over their credit limit. When you combine the customer DD along with the sales order and lineitem DD, this is what you get:
Customer

Sales Order

Lineitem

Now, when saving a new lineitem, the save operation cascades upwards to the customer table and any attempt to save a lineitem that puts them over the credit limit is denied!

VDF has interface features that make it far easier for the user:

Lookups: These are popup lists that (at the click of a button or press of a key) are set up to make finding easy. For example, to look up an order, you might show Order #, Date, Customer, Ship To, Total & Status. The user can really see what they need to do their job efficiently.

Indexing: Put the cursor in the Order # field & you can move back & forth through the table in Order # order. Put it in Order Date & you can browse by Order Date, etc. – no programming required (except creating the indices).

The VDF interface is designed for data entry:

The standard VDF application is MDI (Multiple Document Interface). This allows the user to have 2, 3 or more views of data open at a time, but the whole application can be minimized at one click of a button. It also puts menus and toolbars at the top of the application so they don’t have to be added to each view.

If your users prefer to navigate from field to field with the Enter key (instead of Tab) – add one line of code, recompile & you’re done.

Every action that you can do with a mouse, you can also do with a key or key combination. This means faster & easier entry for skilled users, while allowing the use of the mouse by users who prefer it.

VDF has backward & forward compatibility. An application written in version 9.1 will compile & run in 12.0 (5 versions later) with little or no changes to the code.

VDF pioneered teaming Windows applications with Web applications. A VDF WebApp can easily work with the same data (including the data dictionaries!) that your Windows system uses.

-End Presentation-

Publications:
Your article, "Visual DataFlex Vs Visual Basic - Visual DataFlex Advantages" - has been accepted and added to the EzineArticles.com directory:
http://EzineArticles.com/?id=731962
You've also earned Expert Author status:http://EzineArticles.com/?expert=Peter_Donovan

Subclassing SL in Visual DataFlex

2007-09-10T00:05:00.000-04:00

Hi, while others would think it strange to hear, I have just programmed my first global variable ever and am happy with my decision! As many know, Applause Software is a North American Mfg's rep for Soft Sys which is currently negotiating a VDF 12.1 release of it's proven VDF7 verticle market product named "MASS" (Membership Administration Software Solution). This work is for that project. Much of the code design involves making all instances of a GUI standardized and centralized in coding technique.

Ref: http://www.membershipadmin.com/
Ref: Peter Brooks @ SoftSys: Info@MembershipAdmin.Com

In keeping with my best oops foundation, I have never ever coded a global variable until now. I always used client area properties to communicate between views etc.

The premise:
How to program a selection list or popup dialog to say whether the user pressed OK or not.

Many decisions, especially in views and reportviews need to know if the user changed the value in the dbform or form. Usage of onchange needs to be programmed into each and every dbform or form if this is desired, getting the value prior to forward sending prompt and getting the value after forward sending prompt. Very messy that way.

So:
My global variable is necessary because:
It's programmed into the classes which will be precompiled prior to the client area existing.
Since it's a SL value, each and every dbmodal panel would have to be non-deferred-create if the panel carried the property.

Explanation of this:
Procedure Prompt
Boolean bOk
Set pbOk of (prompt_object(self)) to false // doesn't exist yet! // error!
Forward Send Prompt
Get pbOk of (prompt_object(self)) to bOk // dialog has been destroyed // error!
End_Procedure

The gv: // [global variable]

Boolean gbOK
Contained in the TOP of the custom classes use package.
This way, if the classes are used in another program, you don't have to code the gv again.
My classes for Soft Sys based on the dbModalPanel: (special subclass for selection lists).

//============================================//
Class cSoftSysDbModalPanel is a dbModalPanel
Procedure Construct_Object
Forward Send Construct_Object
// Define new Properties:
Property Boolean pbSelectionList Public False
// Create child objects:
// Set property values:
End_Procedure

Procedure End_Construct_Object
Forward Send End_Construct_Object
// Add your code that needs to be executed at the end of the object construction here:
// This overrides the individual object settings as existed in VDF7
If (not(pbSelectionList(Self))) Set Border_Style to Border_Dialog
Else Set Border_Style to Border_Thick
End_Procedure
// Create and augment procedures and functions
Procedure Popup
Move False to gbOk
Forward Send Popup
End_Procedure
Procedure Set Label String sMyLabel
// intercepts the setting of the label, and does a language [australian to usa] translation!
Integer iPos1 iPos2
If (sMyLabel > "") Begin
If (CurrentCountry(Self) = "United States") Begin
POS "Enrol" in sMyLabel to iPOS1
POS "Enroll" in sMyLabel to iPOS2
If (iPOS1 <> iPOS2) Replace "Enrol" in sMyLabel With "Enroll"
POS "enrol" in sMyLabel to iPOS1
POS "enroll" in sMyLabel to iPOS2
If (iPOS1 <> iPOS2) Replace "enrol" in sMyLabel With "Enroll"
End
Forward Set Label to sMyLabel
End
End_Procedure
// Automatic Save_Header for dbgrids etc. built into dbView-dbModalPanel.
Function DoSaveHeader Returns Boolean
Send Request_Save_No_Clear
If (Should_Save(Server(Self))) Function_Return True
If (IsNullRowID(CurrentRowID(Server(Self)))) Begin
Error DFErr_Operator "Please Enter Info In Top Part Of Entry Form"
End
If (Err) Function_Return True
Function_Return False
End_Function
// Note: See individual topic in previous post for this function!
End_Class
//============================================//
// Note: with search and replace, I replaced the class of all SL panels with this one:
Class cSoftSysDbModalPanelSL is a cSoftSysdbModalPanel
Procedure Construct_Object
Forward Send Construct_Object
// Define new Properties:
// Create child objects:
// Set property values:
Set pbSelectionList to True
End_Procedure
Procedure End_Construct_Object
Forward Send End_Construct_Object
// Add your code that needs to be executed at the end of the object construction here:
End_Procedure
// Create and augment procedures and functions
End_Class
//============================================//
// Note: with search and replace, I replaced all instances of dbLists with this class:
Class cSoftSysDbList is a dbList
Procedure Construct_Object
Forward Send Construct_Object
// Define new Properties:
// Create child objects:
// Set property values:
Send DoDefineShadowedColorUpgradeProperties
End_Procedure

Import_Class_Protocol cSoftSysShadowedColorUpgrade

Procedure End_Construct_Object
Forward Send End_Construct_Object
// Add your code that needs to be executed at the end of the object construction here:
// These setting OVERRIDE the object settings whatever they may be!
// Makes previously coded stuff all uniform now.
Set CurrentRowColor to clYellow
Set GridLine_Mode to Grid_Visible_Both
Set peAnchors to anAll
End_Procedure
Procedure Set Header_Label Integer iColumn String sText
// Another interception of setting the label for a language translation...
If System.Label_Surname gt "" Replace "Surname" in sText with (Trim(System.Label_Surname))
Else If (CurrentCountry(Self) = "United States") Replace "Surname" in sText with "Last Name:"
Forward Set Header_Label item iColumn to sText
End_Procedure
// Create and augment procedures and functions
Procedure Ok
If (Move_Value_Out_State(Self)) Move True to gbOk
Forward Send Ok
End_Procedure
End_Class
//============================================//

So now, in effect, what I am doing with the global variable is setting it to false on popup and setting it to true upon clicking the OK button of the SL or pressing enter to select a record in the SL.

Because it's a global variable, it can be coded into the classes which are precompiled prior to the client area (on the desktop) and referred to in class code prior to the oApplication being executed to open the workspace etc.

End Result in Code: // if you need to know whether the user is getting a variable from the SL:

Object oMyForm is a cSoftSysForm // non data aware such as in a report.
Procedure Prompt
Forward Send Prompt
If (gbOk) Begin
// do whatever you need to do with the value like setting a property to govern the constraints or output options.
End
End_Procedure

//===================================//
End Article!
PAD

SaveHeader Function: an upgrade

2007-09-09T02:55:00.000-04:00

SaveHeader Function

Upgrade Suggested for your dbgrid's saveheader call to allow entry in them:

// DAW coded save_header function.

Function Save_Header Returns Integer
Boolean bHasRec bChanged
Handle hoSrvr

Get Server to hoSrvr // The Header DDO.
Get HasRecord of hoSrvr to bHasRec // Do we have a record?
Get Should_Save to bChanged // Are there any current changes?

// If there is no record and no changes we have an error.
If ( not(bHasRec) and not(bChanged) ) Begin // no rec
Error DfErr_Operator 'You must First Create & Save Main Order Header'
Function_Return 1
End

// Attempt to Save the current Record
// request_save_no_clear does a save without clearing.
Send Request_Save_No_Clear

// The save succeeded if there are now no changes, and we
// have a saved record. Should_save tells us if we've got changes.
// We must check the data-sets hasRecord property to see if
// we have a record. If it is not, we had no save.
Get Should_Save to bChanged // is a save still needed
Get HasRecord of hoSrvr to bHasRec // current record of the DD
// if no record or changes still exist, return an error code of 1
If ( not(bHasRec) or (bChanged)) ;
Function_Return 1
End_Function // Save_Header

// Suggested replacement for same:

Function SaveHeader Returns Boolean
Send Request_Save_No_Clear
If (Should_Save(Server(Self))) Function_Return True
If (IsNullRowID(CurrentRowID(Server(Self)))) Begin
Error DFErr_Operator "Please First Enter Info in the Order Header"
End
If (Err) Function_Return True
Function_Return False
End_Function
// Notes:
// Save Requests never save blank records so it's safe to call at any time
// We don't give an error when changes exist because the errors already have run
// We only give an error if no info was entered at all in the header
// Ref: Garret Mott's whitepaper "Software as a conversation" we say please.
// This function returns a true value for ANY error not just the one that we send.
// We always return a value in a function whether implied or not.

The second function is both less verbose and superior in both coding technique and performance to the code many software engineers have copied intact from the sample examples.

In addition, it can be dropped almost intact into a dbview subclass!

Note: Garret Mott's "Software as a conversation" can be found in the whitepaper section on http://www.nedataflex.com/ and the author can be reached at http://www.automatesoftware.com/

The author, Peter Donovan, can be found at http://www.applausesoftware.com/

Selection List Upgrade #1

2007-09-09T02:37:00.000-04:00

Selection List Programming in Visual DataFlex

Programming a selection [lookup] list in VDF12 can be enhanced with the use of an “enter new” button that allows you to enter a new parent record, and have it “fall thru” the selection list into the data entry program or report.

The selection list has been made such an amazingly easy task by Data Access Worldwide, where a lookup (as pictured below) can be created in just a few clicks and keystrokes.

The Selection List [stock] from the Order Entry Sample Example VDF 12.1 …

The second SL pictured is a great candidate for the addition of an “add new” button.
End result desired pictured here:

… and the add new dialog:

What follows is;

[1] The code from the Modal Dialog
[2] The code from the Selection List

(In VDF 12.1 code)

//====================================//
// dbModalPanel = Popup Dialog for entering new sales person

Use DFClient.pkg
Use SalesP.DD
Use Customer.DD
Use OrderHea.DD
Use DFEntry.pkg

Object SalepAddNewDialog is a dbModalPanel

Property Boolean pbOK
Property RowID priRowID

Object oSalesp_DD is a Salesp_DataDictionary
End_Object

Set Main_DD to oSalesp_DD
Set Server to oSalesp_DD

Set Label to "Add or Edit Sales Person"
Set Size to 83 308
Set Location to 2 2
Set Border_Style to Border_Dialog
Set Auto_Clear_DEO_State to False // no clear on save

Procedure Popup
Set pbOk to False
Send Clear of oSalesp_DD
Forward Send Popup
End_Procedure

Object oSalesP_ID is a dbForm
Entry_Item SalesP.ID
Set Location to 9 91
Set Size to 13 42
Set Label to "Sales Person ID:"
End_Object

Object oSalesP_Name is a dbForm
Entry_Item SalesP.Name
Set Location to 23 91
Set Size to 13 156
Set Label to "Sales Person Name:"
Set Label_Col_Offset to 2
Set Label_Justification_Mode to JMode_Right
End_Object

Object oOK_btn is a Button
Set Label to C_$OK
Set Location to 44 185
Set Default_State to True

Procedure OnClick
Handle hServer
RowID riRowID
Move oSalesp_DD to hServer
Send Request_Save
If (Should_Save(hServer)) Procedure_Return
If (not(Current_Record(hServer))) Begin
Send Info_Box "Please Find Or Enter A New Sales Person ~ Then Click Ok"
Procedure_Return
End
Get CurrentRowID of hServer to riRowID
Set priRowID to riRowID
Set pbOK to True
Send Close_Panel
End_Procedure

End_Object

Object oCancel_btn is a Button
Set Label to C_$Cancel
Set Location to 44 243

Procedure OnClick
Send Close_Panel
End_Procedure

End_Object

On_Key Key_Alt+Key_O Send KeyAction of oOk_btn
On_Key Key_Alt+Key_C Send KeyAction of oCancel_btn

End_Object

//====================================//
// Selection List augmented only for the add new button:

Use DFClient.pkg
Use DFSelLst.pkg
Use Windows.pkg

Use SalesP.DD
Use SalepAddNewDialog.dg

CD_Popup_Object SalesP_sl is a dbModalPanel

Set Minimize_Icon to False
Set Label to "Sales People List"
Set Size to 118 265
Set Location to 4 5
Set piMinSize to 97 174

Object SalesP_DD is a SalesP_DataDictionary
End_Object // Salesp_DD

Set Main_DD to SalesP_DD
Set Server to SalesP_DD

Object oSelList is a dbList
Set Main_File to SalesP.File_Number
Set Ordering to 1
Set Size to 71 248
Set Location to 6 6
Set peAnchors to anAll
Set pbHeaderTogglesDirection to True

Begin_Row
Entry_Item SalesP.ID
Entry_Item SalesP.Name
End_Row

Set Form_Width 0 to 40
Set Header_Label 0 to "ID"

Set Form_Width 1 to 200
Set Header_Label 1 to "Sales Person Name"

End_Object // oSelList

Object oOK_bn is a Button
Set Label to "&Ok"
Set Location to 81 97
Set peAnchors to anBottomRight
Set Default_State to True

Procedure OnClick
Send OK To oSelList
End_Procedure

End_Object // oOK_bn

Object oCancel_bn is a Button
Set Label to "&Cancel"
Set Location to 81 151
Set peAnchors to anBottomRight

Procedure OnClick
Send Cancel To oSelList
End_Procedure

End_Object // oCancel_bn

Object oSearch_bn is a Button
Set Label to "&Search..."
Set Location to 81 205
Set peAnchors to anBottomRight

Procedure OnClick
Send Search To oSelList
End_Procedure

End_Object // oSearch_bn

Object oAddNew_bn is a Button
Set Label to "&Add New"
Set Location to 81 8
Set peAnchors to anBottom

Procedure OnClick
Handle hModalDialog
Move (SalepAddNewDialog(Self)) to hModalDialog
Send Popup of hModalDialog
If (pbOk(hModalDialog)) Begin
Send FindByRowID of (Server(Self)) Salesp.File_Number (priRowID(hModalDialog))
Send Display of oSelList
Send Ok of oSelList
End
End_Procedure

End_Object

On_Key Key_Alt+Key_A Send KeyAction of oAddNew_bn
On_Key Key_Alt+Key_O Send KeyAction of oOk_bn
On_Key Key_Alt+Key_C Send KeyAction of oCancel_bn
On_Key Key_Alt+Key_S Send KeyAction of oSearch_bn

CD_End_Object // SalesP_sl

//====================================//

End Result of Code:

The code above results in a “drop-thru” of the new Sales Person entered and puts their ID/intials in the data entry view without stopping at the selection list.
By
Peter A Donovan
Applause Software
September, 2007

The Theory Of Meaningless Numbers

2007-08-29T03:31:00.000-04:00

The Theory Of Meaningless Numbers (TMN0001)
By
Applause Software
Peter A Donovan

What is a meaningless number?
Meaningless numbers are ID and CODE columns which uniquely identify a record in a database table. They were made up by computer programmers, and in traditional programming, they formed the first entry window where you were responsible for remembering that “D” means Doctor, and “402” is your best customer. Since it would be wrong to discriminate against an entry window just because it’s a letter and not a number [age of equality] I’ll include meaningless letter combo’s in this theory also.

The point?
Users should not be required to remember “402” for General Electric of Massachusetts and “791” for General Electric Turbine Division”, but programmers should indeed still make use of them as the basis of relationships between database table records. Just don’t expect the users to enter or remember them: the truly meaningless numbers and codes can be totally hidden from users and as a study, I will refer to RoloFlex by Applause Software as a good example where each table is based on a unique meaningless number. [reference: http://www.applausesoftware.com/ : free RoloFlex]

What is a meaningful number?
A meaningful number is those database records that are referred to commonly by number such as PO #4067, Sales Order #1, and Speeding Ticket #352-4635A. These numbers exist on paper and are the primary way of referring to a record of this type. When you go to look up my speeding ticket, you might indeed look it up under my name also, but when a payment is received [good luck] you want to be able to enter the printed number 352-4635A and quickly locate and apply payment before my check bounces.

Can a meaningful and meaningless number co-exist?
Yes. Numeric meaningless numbers are the foundation of unique identifiers of each record, and a meaningful number can co-exist as [both] uniquely indexed [findable] columns in the same data table.

There’s a space here while the programmers hold their heads.

Let’s say you are a database programmer and know that numbers rather than a string which varies in length [throwing off the sort order completely] should be the foundation of the database record [for speed and relationship purposes only], you can program your unique (meaningless) ID column of speeding tickets, and also have a unique (meaningful) column which is ascii [mixed numbers and letters] which is used for finding it.

Why not make the key column a automatic increment number for relation purposes alongside a humanly enterable column consisting of alpha-numeric characters? Hands please? How many programmers have written 200 lines of code to auto-increment “#352-4635A”? The role of the meaningless number is to get auto-incremented in 1 line of code, being totally hidden from the user, and the foundation of the relationship to it’s parent database table. The role of the Speeding Ticket number is to humanly find a record more easily than 12342345345565.

Table Layout Proposed:
-Fines-

Column: Element: Type: Length: Index: Relates To:
1 ID Numeric 16.0 1 (unique)
2 TicketNo Ascii 20 2 (unique)
3 VIN_ID Numeric 10.0 3 VIN.ID // Not VIN (Ascii Field)
4 SSN_ID Numeric 10.0 4 SSN.ID // Not SSN (Ascii Field)

-VIN-
Column: Element: Type: Length: Index: Relates To:
1 ID Numeric 10.0 1 (unique)
2 VIN Ascii 20 2 (unique)

-SSN-
Column: Element: Type: Length: Index: Relates To:
1 ID Numeric 10.0 1 (unique)
2 SSN Ascii 11 2 (unique)

This structure makes use of meaningless numbers and meaningful numbers side by side, each fulfilling their job.

Hopefully there is a programmer slapping his/her head here like the V-8 commercial.

The ROLE of a meaningless number:
Let’s face it. Meaningless numbers are here to stay. Everybody’s got one, but programmers are still stuck on what to do with them. HIDE THEM! In a relational database model, where the child is related to it’s parent by the ID, the value will automatically drop down to the child upon a successful save, making display of this number absolutely unnecessary. I should point out that many good programming firms are based on “Intelligent Design” such as Auto-Mate Software of the USA http://www.automatesoftware.com/. Please visit this site to read about the story about “Enter the field matrix number”…. It’s a great story.

Let’s go a step further and call a byte a byte. Whether it’s a field matrix number or a part number, due concern needs to be put into the design of a “key field” lookup to determine whether or not it’s meaningful or meaningless. On a part number, why not both? To programmers, here’s my argument: why not use this technique so that if the part number is mis-entered, or changes, you can simply reenter the part number without altering the relationship? Madness or magnificent? It’s your opinion that counts.

Let’s take an example in RoloFlex 12.3 from Applause Software (open source and freeware). The database tables all have a unique ID that is 10 digit numeric: Please refer to the running program and you will see that none are visible. In addition, I have coded the key fields as “noenter” so that if they were made visible, they could not be used! Ten digit ID numbers for everything? Meaningless or Madness?

Hands again? Each programmer who has had to increase a user’s key ID field from 6 to 8 to accommodate 20 years of data entry please stand up! I’ll bet there are a good many among us. Let’s also note in passing that dates on computers are stored as 6 digit integers, and in the western world we are almost out of numbers in the six digit length! Why have we not expanded our dates to 8 or 10 digits? I guess we’ll have to wait until “Y6K” to find out!

The design of meaningless numbers in action:
Let’s take on a RDBMS [relational database management system] example and specifically look at parent and child table design. My first point should be obvious to most programmers, that a parent ID field is used to uniquely identify the parent but (being meaningless) is not displayed to the user at all. In RoloFlex, please note that the parent database tables of the main table have a unique ID which drops down into the main table upon a save, forming the relationship without being seen.

Please note (when inspecting the inner table def's for RoloFlex tables) that the Key ID column has a noenter attribute, meaning that the user cannot change or type in a new value to that column should it appear on the screen. It is auto-incremented from the system file “sysfile” and is totally meaningless to even the database designer other than being a unique value. No surprises here, but let’s look at a child table to see the same technique:

So, what’s the surprise here? On many occasions, I have noticed the lack of a single unique key field on child records. For example, the child of order header would have a key combination of HeaderID and Linenumber. If I applied the same consideration to the CallHist table, then there would be a combo of RolodexID and Call Date as the first index. What [the used] this technique does is to form the basis of a future child table to CallHist. From the get-go, a strong ID field exists to form a potential one-to-one column relationship to a child of CallHist which may exist in the future. The point, then, is to always program an ID column as a unique meaningless number for every table and index it accordingly. Then, progress onwards to specifying all the other columns of the database table.

As an extra bonus, you will see that “recnum” or record number is not defined in any of the indexes making a move from any one back end to another manufacturer’s back end a relatively easy job.

Whitepaper Summary:
I believe I have defined the difference between a meaningful number and a meaningless number and stated that meaningless numbers have no place in data entry! On the other hand, the argument for placing a meaningless number as the foundation of your relationships overwhelms the reasons that you might have for designing a meaningful number as the relationship key: It is my contention that an alphanumeric or string column has no place as the relationship key, and lastly that each table should have an ID field for forming the relationship which totally frees you to change the secondary key column with data entry without compromising the relationships.

Let end users see meaningful numbers only, but put your foundation on “meaningless design” with [hidden] data architecture!

Modern Sales Theory Explained: The Funnel Theory

2007-06-24T21:34:00.000-04:00

Author: Peter A Donovan of Applause Software.

The Funnel Theory:

First: The Funnel:

The Funnel is a way of describing your prospect base that is used by ACT and GOLDMINE as their basic premise. The problem with both of these 2 most popular packages in my opinion is that they include so many extra functions in order to sell their product that the basic intent of their system gets lost by users with little or no training and even by veteran users.

Imagine a funnel, like a megaphone with a large open side on one end and a small open side on the other.

Many businesses find themselves in business for 30 years and the sales department has information on about only 20% of the potential market due to turnover, record keeping on paper (unusable in many cases because of being outdated), and general policy of not understanding the funnel theory.

The premise:
The large side represents how many potential accounts you know about in order to be able to contact them and sell your services to.
The small side represents prospects who are ready to make a yes/no decision on a quote or proposal or bid you make and a percentage of these will fall through the small end and become sales.

4 Goals:

1. Increase the funnel by marketing, cold calling, meetings, conventions, inbound phone calls, etc. Premise: The more in the funnel, the more fall thru as sales.
2. Increase the number of prospects at the small rim of the funnel, thereby (making the assumption that your closing ratio stays the same) you get more sales.
3. Skew the funnel with leads that are more likely to be sold. This is done by accessing your funnel lead base and marketing (cold call/direct mail, etc) to a proven segment of the market with a higher closing ratio, or customers where you have an add-on product for what they use.
4. By whatever means including skewing the funnel and teaching modern sales tactics to the field reps, you increase your closing ratio.

6 Assumptions:

1. The more leads in the funnel brings more opportunity to sell your product. If you don't have a way of regularly contacting the entire funnel this assumption is meaningless. Therefore you must generate advertising directed individually at each funnel listing via phone and mail and email.
2. The more information you gather about each funnel lead brings you closer to a sale. You can't sell an account unless you know the name of the decision maker or beginning contact person. You can't determine the value of the account to you without knowing what size the account is, what potential they have to be a client, or information that would make them non-desirable as a customer. If you don't have this information, and a way of using it to select segments of your prospects for contact it's useless.
3. The more frequency of calls to your best market segment leads to higher sales volume. You must have information to fuel this market segment and identify it.
4. Price is meaningless in many cases. You must present yourself to situations where you are the only bidder or have identified the needs of the customer properly and prove both in speaking to the prospect and backup in print that their needs will be best addressed by your company. If you don't save this information for future use [assuming no sale] you put yourself back in time having to do this all over again and lose the ability to skew the funnel based on the information you gather.
5. You must have a way of reporting the funnel. You must have a list of prospects considering a quote ready to make a decision. You must have a list of each field rep's active accounts that they are pursuing. You must have a way (mail merge, email blast) of regularly putting your name in front of the target market based on the info collected.
6. From #5 you must have a way of determining if the inner funnel leads are sold or lost or postponed. This gives you a closing ratio which is the heart of the funnel. To explain, you must log a history that a quote was given, and have a history of which of these resulted in sales (otherwise you can't compute a closing ratio) after the fact. Monitoring activity of leads (the number active), the prospects on the inner edge with quotes, and keeping track of field rep closing ratios over time gives you a pulse.

2 Rules.
1. If a field rep produces many sales you can't touch them and they can do anything they want until the sales stop flowing. To keep this salesrep on top of the heap you must provide them with incoming leads of a high quality which they will only pursue a percentage of due to their status.
2. Longevity and Burnout. The longer you keep the top salesreps as employees, the closing ratio will increase and sales will increase, and it will become easier to project budget and rely on your projections. The supply of quality leads to these reps is the key to keeping them longer.

Your goals as business director is to make everyone understand the funnel theory as explained above and make the:
FUNNEL, the HEART, and the KEY in your sights and produce the needed reports, mailings, etc. to make it happen. You must skew the funnel to do this and keep your eyes on the pulse.

Regards,
Peter A Donovan

Applause Software
Wakefield, MA USA
(781) 968-5240

Upgrade For Free ROLOFLEX Published Today

2007-04-14T17:11:00.000-04:00

In a previously announced release, a fully featured contact manager and personal information center named RoloFLEX written in Visual DataFlex by Applause Software was upgraded to include the following features:

*** UPGRADE TO ROLOFLEX AVAILABLE ***

Please see http://www.roloflex.biz/ for downloading the free RoloFlex.

New Features Include:

1. An active toolbar that has these features:
* Shadows the find keys when not in an indexed field.
* Shadows the delete key if a record is not found.
* Shadows the save keys if no changes exist to be saved.
* Puts the DELETE button WAY AWAY from the SAVE button.
* Offers A Save and Clear, or a Save and No Clear. etc.

Thank you to Vincent Oorsprong of DAW Netherlands and Peter Brooks of
Soft Sys/Australia (www.MembershipAdmin.Com) for the ActiveToolbar.

2. VDFQuery is part of the file structure now (The 2.4 beta)
* You can compile now right away without having to path to VDFQuery.

Thanks dearly to Sture Anderson of DAW Netherlands for sharing VDFQuery.

3. VDFSORT Included.
* International Downloaders not in USA English must reindex prior to using.
* This tool is now included without having to use database builder.

There have been over 1000 visits to the download page of RoloFLEX and if you
haven't tried it yet please give it a shot as it is well constructed and highlyuseful.

Thanks to all who visited my website in the process.

Peter A Donovan
Applause (TM) Software
Wakefield, MA USA

***NOTE: THIS UPGRADE DOES NOT INCLUDE THE DATA OR LETTERS FOLDER SO IT IS SAFE TO DOWNLOAD OVER YOUR EXISTING APP. I DID.

Steps:
1. Install Personal Version Of VDF12.0 (Link On My WebPage)
2. Install RoloFLEX 12
3. Install Updgrade1

Hope you enjoy.

Note: this fully featured RoloFLEX is totally free and includes source code (open source)
and is based on a free personal edition of Visual DataFlex studio by D.A.W.
(Data Access Worldwide of Miami USA)

Note: If you find this RoloFLEX useful for BUSINESS NEEDS there are 2 comments I would
like to make:

1. A runtime license (extremely inexpensive) is required for business use. I would be happy
to quote you pricing on this license.
2. Customization: If you would like RoloFLEX muscled up for your specific business needs
please contact Peter Donovan of Applause Software for a quotation on such.

All the elements mentioned above are freeware with no expiration date for personal usage and to get accustomed to ~the best kept secret~ in the Database Visual Studio industry.

Trademark Turnaround!

2007-03-16T19:46:00.000-04:00

[Title:] Trademark Turnaround

[Header:]
Concerning the trademark of Sonata Software LTD previously posted by Peter A Donovan was an article concerning a trademark owned by Sonata Software LTD which could be construed as criticizing Sonata Software LTD for enforcing such.
This is an apology letter to Sonata Software LTD concerning same.

[Article:]

Points Of Apology::
Since I posted my article about Sonata Software LTD enforcing their trademark on the word Sonata in conjunction with developing and marketing business software I have come to realize that;

1. They have every right to enforce their trademark since I had references to my former business under a similar name on the web describing me as performing the same functions as the trademark held by Sonata Software LTD..

2. If Sonata Software LTD did NOT enforce their trademark they could set a precedent which could negate their trademark and damage the company’s investment.

* Now, my business (renamed) is in the same shoes as Sonata Software LTD (Applause TM Software) where I am "composing" this letter to say that I must now also enforce my trademark in the same manner as Sonata Software LTD on the word "Applause" in conjunction with developing and marketing business software and creation of dynamic content web sites.

Apology:
In my dealings with the Attorney for Sonata Software LTD I have been treated with patience and they have taken the time to explain our mutual dilemna and their position as described above with courtesy and professionalism and I now regret any aspersions I have cast against this company in my previous post in my journal news story and blog.

Where I went wrong!:
I began my DataFlex software business license in 1991 from Data Access Worldwide under the name of Sonata Software without checking if a similar business existed under the same name. For me, the term "Sonata" was a personal term for "moonlighting" since the Moonlight Sonata is my favorite musical composition by Ludwig Van Beethoven, Sonata #14. The sonata is the third most common form of classical musical venue after the symphony and the concerto.

I am hereby giving up all claims to the company name "Sonata Software" and moving on to Applause Software, operating the same business began in 1991 under a new name.

I am also moving the ownership of 2 previously operated sites "SonataSoftware.US" and "SonataSoftware.Biz" to Sonata Software LTD as part of our settlement agreement which meets my approval since I do not operate either anymore.

Former Clients Of Peter A Donovan:
Please find me now at http://www.ApplauseSoftware.Com (781) 968-5240 Still in the same location.

Applause TM Software: A Visual DataFlex Consultancy:
Nothing except my new business name Applause TM Software (I am learning) has changed except the name transition, and Applause Software is the hoped for end result of my efforts for each client!

My Trademark Applause.:
Applause designates my business of developing and marketing custom software for business needs and for developing (currently Electos from the maker of Visual DataFlex) dynamic content publishing websites.

DataFlex:
DataFlex began in the days of CPM when "I-CODE" and when DOS began, DataFlex was in the forefront of options and was chosen by a great many companies for it's "FLEX" ability and the English language syntax which is easy to learn similar to COBOL.

My Toolset: Visual DataFlex:
VDF, or Visual DataFlex is the PC (Vista/Windows) version of DOS DataFlex which has been successfully migrated to a world class development studio for database and web to database applications in a RAD (rapid application development) environment especially and specifically suited to database programs.

Backends and FrontEnds:
A "backend" is the database operating environment behind the screen where the data is saved. Visual DataFlex is a "transparent front end", creating programs that can run on most major "backends" such as DataFlex itself, Express SQL, My SQL, IBM DB2, Pervasive, etc.

Sonata Software LTD Clients and Prospective Clients:
If any person reading this review is seeking to contact Sonata Software LTD please do so at www.SonataSoftware.Com.

Summary:
Intentions: In any future dealings with other companies named "Applause" involved in the same business as my trademark, I intend to extend the same professionalism and courtesy that Sonata Software LTD has shown me.

NEW: Free Database Development Studio

2007-01-07T06:14:00.000-05:00

1/1/2007
Just Released From Data Access Worldwide Of Miami.

Freeware database application development studio with no restrictions other than for personal use.

Visual What? has been our bane of existance because we utilize a world class development tool that isn't known by most developers. A Personal Edition of "VDF" is released is so that you can discover the power and rapid development abilities of this system which includes a PC/windows program creator, (WebApp) a web application extention (interface your data with the web), and (Electos) a dynamic content publishing website creator.

"Our most valuable asset is the easiest to market free", a quote by the CEO of Data Access Corp.

Here's the scoop: Visit my website for BOTH a free copy of Visual DataFlex AND a free personal rolodex application which shows the abilities of this tool. I personally am adding both a freeware application which anyone can use for personal reasons (see site for pic) and an offer for a discounted business version once you've decided that this system is desireable for business use.

Data Access is following the example of many other vendors such as MS SQL which now offers a free 25 user "Express SQL" with many of the development features removed from the product. NOT SO with the Personal Copy of Visual DataFlex: you get everything with the agreement that only personal use is allowed.

So, therefore, I offer this personal application which lets you auto-dial, email, save pictures of your contacts, save contact history, report on callback dates, and easily filter your entries by source of entry or category of entry plus letter writing options etc. It's a powerful application for real world personal use so that you can see the power of "VDF". There is also a link to video instruction in VDF where over an hour of presentation on concepts as applied to Visual DataFlex coding may be obtained from Sonata Software.US See: http://www.ApplauseSoftware.Com

The hope of Data Access is that the "geeks" out there (me being one) will download, play, and discover how great this system really is, and how easy it is to develop a rapid application deployment system whether it's PC based software, web data integration, or website CRM publishing.

It is my personal hope that my contribution will lead to new "VDF" developers in the near future. We have a camaraderie amongst "VDF" developers where we share code and help solve others problems and have a number of Newsgroups for help and support, plus a huge online help directory for personal research on the spot.

So, why not take a double freeware offer: the entire development system of a 4GL language which contains sample examples on how to implement usage, and a freeware personal example that you can use immediately with no cost or expiration date? http://www.ApplauseSoftware.com

Quoting from the "Blues Brothers" movie: "It's 106 miles to Chicago, we got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses: HIT IT!"

Looking forward to seeing your name on the VDF newsgroup, sincerely Peter A Donovan.

Top 2 Reasons To Use A Visual DataFlex WebApp

2006-10-27T05:28:00.000-04:00

Top 2 reasons to interface your current data with the web with Visual DataFlex Web Applications

Visual DataFlex WebApp (TM of Data Access Worldwide of Miami) is a tool used by (Applause Software) and the (NEDC) two of the premier Visual DataFlex specialists in the USA.

Type 1

Your website collects prospect data in the form of email or CSV and you must manually compare the results to your prospect database and manually type in new data thru your windows or dos programs. Some companies write scripts to "parse" the email but changes to the email format require reprogramming and the "batch parsing" routines make response to the emails slow.
With a Visual DataFlex WebApp, your incoming queries from the web are automatically fed directly to the correct on-file customer or a new customer/prospect record is created. When the prospect lead comes in, you feed the inquiry directly to the sales manager via email (to assign to a CSR or salesrep) and a reply email is sent back to the inquirer with your chosen text indicating that you received their information and that you will be in touch shortly. Determination if the inquiry is a customer or prospect is made instantly at the time of the inquiry and response time is immediate. Example of Type 1 LIVE Visual DataFlex WebApp: Sports Travel And Tours Inc.

Type 2

Your phones are ringing too much with customer inquiries that could be eliminated thru a sharing of data online where the customer logs into their account and can view their inventory, outstanding debt, status of sales orders, etc. (customized to your need) and save the phone from ringing.
With a Visual DataFlex WebApp from Sonata Software, or NEDC, your chosen data is shared securely in a customized format designed by you, and passes thru a login page to data that has 4 levels of security built into it including a datadictionary object that determines whether data can be changed/entered, etc. based on your needs. A subset of your data can be shared on a dedicated PC running XP Pro: no need for investment in a Linux or Unix based server thru a technology from Microsoft called IIS (internet information services).
Bonus: Your data does not have to be in a certain format: Visual DataFlex and WebApp are transparent "front ends" which can share and collect data to DataFlex tables, MS SQL tables, IBM DB2 tables, etc. or a combination of all.
Both these options give you 24/7/365 presence to serve your market.
Example of Type 2 LIVE webapp: American Data Storage Inc.

Project: Stop The Phones From Ringing With a Visual DataFlex WebApp Database Sharing Application

2006-10-27T04:56:00.000-04:00

Client: American Data Storage of Boston, MA (www.AmericanDataStorage.Com)

Client Problem: My phones are ringing off the hook with inquiries about inventory requests and the manpower I have is being sapped by these inquiries to the point of not allowing us to perform our regular duties and we have a backlog of work.

As a software engineer with 23 years in the custom software business, I chose a tool called Visual DataFlex WebApp from Data Access Miami whose main website is http://www.dataaccess.com/. The reason I chose this tool is that it is data-centric rather than interface-centric. Instead of defining a beautiful interface in 10 hours and spending 80 hours in interfacing with the customer's data, I chose a tool where I invested 20 hours of data interface time and touched up the user interface .asp pages over time (20 hours more) and delivered the application at a lower cost than a Studio like .NET or VB because the
Visual DataFlex Studio (rev 11.1) starts at the data interface and automatically (after defining the business rule layer for sharing data) creates the .asp pages which are totally functional but not beautiful.

I have spoken with a number of Sales Marketing Executives including a 500 billion dollar company Marketing and Sales VP, and they have spent huge amounts of effort and dollars invested in web / data interfaces with the .NET and VB Studios. The story from them is very similar: in a very quick time they get a beautiful contemporary interface to do the job, but enforcing business rules such as who gets to see which data, which subsets of data are available, and whether a particular user can delete/edit/create etc. individual data tables at which times is a nightmare that sometimes is unacceptable in the end and costs huge investments in making a web tool compatible with data business rule layers. In addition, the result is that these business rule layers reside in the .asp rather than in (available only thru Visual DataFlex WebApp) a dynamic datadictionary class for each table, and customized data dictionary objects for each module (business rule exceptions to the main blueprint but for an individual module only).

The DataDictionary Classes From Visual DataFlex WebApp function on 4 levels:
1. You are able to define attributes to each column of each table, such as capslock, required entry, comboform values (must be one of....)...
2. Methods are written (functions/procedures) and hooked into the desired columns of each table which are run prior to agreeing on a save or delete.
3. The DataDictionary Class has a cascade of messages that get called upon a new save, an edit to an existing record, or on all saves, or on a delete.
These messages are customizable (say to drop down a parent value into a child table), assign a unique ID to a new record, etc, and lastly validate the data after all the massaging is done to centralize the rules: example: if the total result of the transaction makes the customer overlimit on credit limit you can rollback the transaction entirely based on this level of control.
4. This is the best part: DataDictionaries for each related DBMS table are organized in tree fashion and hooked together so that the data structure of the table is REQUIRED to use datactionaries from it's related parent and child tables. This is called a DDO TREE. Layman's terms: You are saving a new customer, but because the customer table is connected to the terms table, you cannot save a customer unless a predefined record is found by the terms datadictionary object. No save: you haven't selected terms for the customer.
Now, for business modules, the DDO Tree is instantiated for each individual module. You can actually augment the find/clear/save/delete/validate business rules for each module easily and customize them for that particular module. Example: show only the fire protection inventory and hide all other.
Let's get back to the client's application specifically:American Data Storage specializes in keeping inventory of film media, video, and digital video and CD's and targets Advertising Agencies, Broadcasters, and Corporations that do videos for training new employees and advanced study for existing employees. In a bold move, ADS has offered the City of Boston an online, immediate retrieval of all their video surveilance tapes which, in this day of terrorism and crime, is an excellent choice. Instead of trying to maintain (and then locate) certain video, they would login to ADS, search for the inventory, and pick it up within an hour at ADS's main site or have it shipped overnite.

I crafted, in a very low budget, a highly dependable Web Interface to data over the internet which accesses inventory ONLY for the company logged in, and divided into categories or sub-clients of the client, featuring 6 search engines to locate the data and a shopping cart withdrawal of inventory.

The owner of ADS was so pleased, based on his review of the end result, that he hired Sonata Software, (The Author) to create a DEMO AREA where you can login as DEMO and try out the application based on an inventory of popular movies on DVD (all demo, none available in real life). This acts as a promotional piece for the company and it is now swamped with inquiries due to only word of mouth, from new customers and existing customers that want to be able to search for, and order their inventory online 24/7/365.

ADS and I invite you to review the final result and run the Web Application in DEMO MODE at http://www.americandatastorage.com/ (login page).

The results will speak for themselves, and you can contact ADS thru their website to ask how they feel about Visual DataFlex WebApp and what it's done for their business.

Sincerely,
Peter A DonovanOwner / Lead Programmer
Sonata Software: Applause (TM) Software
Boston, MA, USA

Visual DataFlex Product Review

2006-10-27T04:26:00.000-04:00

Visual DataFlex is a database RAD (Rapid Application Development) visual studio where windows and web database applications can be designed.

~The best kept secret in database development~

This article is meant for viewing by mid-size and small companies seeking a lower cost or more rapid alternative to Microsoft platforms such as .NET and VB.

================= Here's the Index For This Article: ===============
* Where did Visual DataFlex Originate?
* What advantages does it have over .NET and VB?
* Why should I try Visual DataFlex (download eval)?
* Who makes Visual DataFlex?
* What support would I receive from Newsgroups Or Support Groups?
* What's the future of Visual DataFlex?
=====================================================================

* Where did Visual DataFlex Originate?
--------------------------------------
In 1981, along with DBASE2, FOXPRO, etc. DATAFLEX (the dos version) launched it's 2.3 version for DOS, CPM, and UNIX.Because it was the highest price database engine and development platform, and it's specs outweighed the competition many individuals who were not programmers purchased DATAFLEX and with it's english like syntax became faithful followers and many success stories were launched. If you were an accountant, sales manager, or inventory analyst, DATAFLEX was perfect since it was a 4GL product and handled the interface with the database included in the package automatically for you, and a winning combination of work skills and easy database development combined to make v2.3 a highly successful endeavor. The packages written in this era were from experts in the field and while many unorthodox methodology was employed, it worked! Unfortunately, like many other (now) Legacy Systems written for DOS became more and more difficult to deploy and maintain since Windows was introduced. There are many DOS DATAFLEX applications still fueling businesses across the world now and most are considering: port to Visual DataFlex, or port to the Web? The main concern of many companies is that unique and proven code which runs like lightning would be compromised by eithe of these solutions, and is generally a real concern: but of significantly less importance than the users perceive.

* What advantages does it have over .NET and VB?
------------------------------------------------
Imagine you are a designer of software, and a .NET solution from Microsoft is available. First, you start with the user interface, and the tools to produce an interface in windows/web are highly attractive. Then, you have the job of writing an interface to the data which is a huge undertaking and requires thousands of lines of code to produce a stable application that follows the specs of database table business rules, connections between database tables (dependencies, etc).

Now, Imagine you are a Visual DataFlex designer. First, you start by subclassing the controls provided by Data Access Worldwide (true windows controls) and leave these subclasses (based on your business name for instance) completely alone and unchanged.... but for future use. Then, you open the database builder which creates datadictionaries for each and every database table in your project, relate the database rules to each other (auto-generated) and determine how each column of each table will appear, which validation will apply to it, and set your business rules directly in the CLASS for the table.

See how the two approaches are completely the opposite?

Visual DataFlex centralizes on data validation, finding, clearing, deleting, and saving, and then you use the Visual Studio to create the visual portion of the program which is built on a TREE of connected data dictionary objects (instantiated business rule layers based on the classes) which can introduce business rule exceptions and augmentation.

The advantages appear immediately:
1, Data Integrity and business rule layers intertwine and you MUST validate the data (automatically generated validation based on your rules) and synchronize together in order to save a record or records.2. The visual designer has the same classes for the most part as .NET and VB but they are tied into database definitions and take on immediately a save/clear/delete/validate/find operation that does not need programming.
The combination of these two advantages means that your data integrity is higher, your data operations are more eloquent, and also the interface (while not quite as beautiful as .NET) is visually appealing.
The design and deploy time from start to finish is less than .NET by a estimated 40% resulting in lower cost to your customer and more winning bids for you.

* Why should I try Visual DataFlex (download eval at www.VisualDataFlex.Com)?
-------------------------------------------------------------------------
First, from the above, you can see how a database oriented approach is significantly easier than other options. Don't download VDF to program a game! It's built for business applications as a specialty, so if that's what you are programming I suggest you give it a try.
Second, the VDF community is closely knit and we publish free code and add-ons, answer questions immediately and with great skill on the newsgroups, and you will belong to an elite membership where close relationships with other developers is quite attractive.

Visual DataFlex is a transparent front end for just about any database back end you care to use such as MS-SQL, IBM DB2, etc.

If you are afraid of being sacked for using a non-Microsoft product, please disregard this article entirely!

* Who makes Visual DataFlex?
----------------------------
The answer is surprising. Of course, Data Access Worldwide of Miami FL USA makes the product, but it is crafted largely thru suggestions of individual developers who receive personal feedback from company representatives on our newsgroup forum, and feedback at conventions personally. Imagine that you too can shape the direction that the product flows and your actual bug reports are included with the fixes in the next release! Credit where credit due.Data Access also has worldwide distributors and is a global product used in many countries.

*What support would I receive from Newsgroups Or Support Groups?
----------------------------------------------------------------
Example: If you are from New England, USA, you can join the NEDC User Group at http://www.nedataflex.com/ which welcomes developers and has regular meetings in person to promote camaraderie and show tech presentations on current projects by the members.In addition, there is a Visual DataFlex newsgroup which is monitored by Data Access Tech Support to some degree, but the feedback comes mainly from globally based Visual DataFlex developers and I personally recommend this newsgroup due to the high quality support received (and given) over the years.

*What is the future of Visual DataFlex?
---------------------------------------
Data Access Corp has network partners over many locations that introduce the latest features available such as SOAP, AJAX, activeX, Web Services, etc. and is about to launch version 12 which will look very familiar to .NET developers. In addition, the ~FREE Personal Edition~ which includes the entire studio and all connectivity kits with a 5 user limit will be unveiled at the next global meeting called "Synergy" in Miami Beach FL in 2007. The promotion of this product will be largely word of mouth and this keeps the tradition and nickname of the product as ~The best kept secret in database programming~ alive!

I invite you to pop open a search engine and search for Visual DataFlex to see what all of the (not(fuss)) is about!

Author: Peter A Donovan of Applause (TM) Software
Peter has been developing custom database applications since 1982 and has migrated his development techniques thru DOS/Windows/Web and oops programming specialization thru centralized coding in both Window/Web and Crystal Reporting.