Resources for “An Introduction to Gambas”

Resources for the print article.
______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

An Introduction to Gambas

Bob Ewart's picture

Interesting article. It would be even more interesting if the application even worked.

Problems I've discovered so far:

1. Database -- table listing has fields status_id and status. Status_id is never referenced. (Maybe used in following articles?)

2. Text tells us to create combo boxes cmdBugId and cmdStatus, but code refers to cmbBugId and cmbStatus. (Typo?)

3. Text never tells us how to get from the first form to the other two.

4. btnAccept calls dat.coder_id which is never defined.

5. The downloaded files do not include the .project file or .gambas folder. Which is ok since it is obvious that the author never tried to run the program.

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions