4th Dimension Learning Basics

Key Takeaways

• The 4D learning path has three layers: relational design theory, 4D-specific platform knowledge, and community/mentor resources — most beginners skip the first and struggle later.
• Books like Inside 4th Dimension and Programming 4th Dimension: The Ultimate Guide remain valuable because 4D’s core concepts (tables, fields, relations, forms, methods) have stayed remarkably stable across versions.
• The 4D-NUG archive (Monkeywerks) and Dimensions Magazine represent the institutional memory of the 4D developer community — searchable, practical, and often more useful than official documentation for real-world problems.
• Relational database design fundamentals (normalization, keys, referential integrity) are platform-agnostic and worth learning from dedicated texts, not just 4D manuals.
• A beginner should budget time for both structured reading and hands-on database building — the two reinforce each other in ways neither does alone.

---

Why the Learning Basics Matter

Every development platform has a moment where a newcomer either “gets it” or quietly gives up. For 4D (4th Dimension), that moment usually arrives when you try to move from clicking around the Design environment to actually building something that works — a table structure that holds together, a form that behaves, a method that does what you intended.

The resources collected here are the ones that have historically helped 4D developers cross that gap. They fall into three broad categories:

• Relational database theory — the concepts that apply to any database, not just 4D.
• 4D-specific references — books and guides written for this platform.
• Community knowledge — magazines, mailing list archives, and developer sites.

Understanding why each category matters is more useful than memorizing a list of titles.

Relational Database Design: The Foundation Nobody Teaches You in 4D

4D is a relational database management system. That phrase matters. If you don’t understand what a relation is, why normalization exists, or what a primary key actually does, you will build databases that seem fine for a month and become unmaintainable within a year.

Three classic texts are worth knowing here:

• Relational Database Design Clearly Explained by Jan Harrington (AP Professional, 1998) — a readable introduction aimed at people who need to design real databases, not study theory for its own sake.
• Inside Relational Databases by Mark Whitehorn and Bill Marklyn (Springer, 1998) — a more thorough treatment that explains why relational systems work the way they do.
• Handbook of Relational Database Design by Candace C. Fleming and Barbara Vonhalle — a reference-style handbook useful when you need to look up a specific design pattern.

These books predate modern cloud databases, but the underlying principles — normalization, entity-relationship modeling, referential integrity — are the same ones formalized by **E. F.

Codd** in the 1970s and still taught today. If you want a free primer, the Wikipedia article on database normalization is a reasonable starting point, and the broader relational model article explains the theory behind it.

A Practical Rule for Beginners

When you design your first 4D database, ask three questions before creating any table:

1. What single thing does this table represent? (A customer, an invoice, a product — not “customer stuff.”)
2. What uniquely identifies each row? (This becomes your primary key.)
3. What does this table depend on, and what depends on it? (This defines your relations.)

If you can’t answer all three, you’re not ready to build the table yet.

4D-Specific Books and References

Once you have the theory, you need platform-specific guidance. The 4D ecosystem has produced a small number of genuinely useful books over the years.

Inside 4th Dimension

By Steve Hussey and Geoff Perlman, this is widely regarded as a good beginner’s book. It covers most topics a new developer needs and, while written for 4D version 6.0, remains very similar in structure to 6.5 and later. The publisher site is inner-dimension.com.

Geoff Perlman later went on to found 4D, Inc. in the United States and eventually Real Software, the company behind the REALbasic/Xojo programming language — a useful reminder that the 4D community has always overlapped with the broader Mac and cross-platform development world.

4D A–Z

Also by Steve Hussey, 4D A–Z is a CD-based reference delivered as PDF files. Its selling point is completeness: it aims to be the most thorough reference guide to the 4D family of applications and plug-ins. The information is stored in a searchable 4D v6.5 database, which is itself a nice demonstration of what 4D can do. See inner-dimension.com/Pages/4DAtoZ.html.

Programming 4th Dimension: The Ultimate Guide

By David Adams and Dan Beckett, this book is notable for being full of real-world experience and recommendations from working MIS veterans and consultants. It’s less of a tutorial and more of a “here’s what actually works in production” guide. Related material is available at island-data.com, including a collection of papers and a well-known article on normalization in PDF form.

4D for Fun & Profit

By Walt Nelson, this is a survival guide for professional 4D developers rather than a technical manual. Its premise is straightforward: if you’re doing work the market needs and you enjoy it, you’ll put in more effort, more hours, and more pride — and eventually earn more. The harder question it addresses is how to keep 4D programming fun after the novelty wears off, when you’re trying to make a living from it. See waltnelson.com.

Choosing Between Them

Book	Best for	Style
Inside 4th Dimension	Absolute beginners	Tutorial, broad coverage
4D A–Z	Reference lookup	Exhaustive, searchable
Programming 4th Dimension	Intermediate developers	Real-world advice
4D for Fun & Profit	Freelancers / career builders	Business and mindset

If you can only buy one, start with Inside 4th Dimension for the concepts and use the free community archives for everything else.

Community Knowledge: Magazines and Mailing List Archives

Books go stale. Communities don’t.

Dimensions Magazine

Dimensions was an eight-year-old, bimonthly, 60-page technical journal for 4D users and developers. Its feature articles tended toward intermediate and advanced material, written by members of the 4D developer community and staff from ACI (the company that produced 4D in its early years). Each issue typically included at least ten feature articles, regular columns, and third-party product ads. Subscribers could receive an examples disk containing the databases authors supplied with their articles — a genuinely useful feature that most magazines didn’t offer. The site was dimensionsmag.com.

The 4D-NUG Archive (Monkeywerks)

The 4D-NUG was the 4D North American Users Group mailing list, and its archive — maintained by PDM — covered over eight years of messages. This is the closest thing the 4D world has to a searchable institutional memory.

The archive is less than perfect, but with minimal trial and error you can usually find what you need. The key skill is knowing what to query for. For example, searching for “toolbar” using the message-subject option would surface a thread titled “Windows stuck under toolbar” with a question and three separate answers. That kind of practical, hard-won knowledge rarely makes it into official documentation.

The archive lived at pdm-inc.com/monkeywerks/monkey.html.

FourDzine

A site maintained by Steven Willis, FourDzine (pronounced “for design”) was another community resource for 4D developers. See 4dzine.com.

How to Actually Use These Resources

A common mistake is to treat this list as a shopping list. A better approach is to sequence it.

1. Week 1–2: Read a relational design primer. Don’t touch 4D yet. Sketch a small database on paper — customers, orders, line items.
2. Week 3–4: Work through Inside 4th Dimension or the equivalent beginner material, building the database you sketched.
3. Month 2: When you hit your first real problem, search the 4D-NUG archive before posting a question. You’ll learn more from reading three answers to someone else’s problem than from getting one answer to yours.
4. Month 3+: Pick up Programming 4th Dimension for the production-grade advice, and consider 4D for Fun & Profit if you’re thinking about doing this commercially.

Signs You’re Ready to Move On

• You can explain why a table is in third normal form without looking it up.
• You can predict what a 4D method will do before you run it.
• You’ve solved at least one problem by searching the archive rather than asking.

Common Pitfalls for New 4D Developers

• Skipping normalization. It feels like overhead until your first data-integrity bug.
• Treating forms as the database. Forms are a view; the structure is the truth.
• Ignoring the archive. Most beginner questions have been asked and answered many times.
• Learning only from one source. A book, a magazine, and a mailing list archive each teach different things.
• Assuming version differences matter more than they do. The jump from 4D 6.0 to 6.5, for instance, changed less than beginners expect.

Frequently Asked Questions

Do I need to learn relational database theory before learning 4D?

Strictly speaking, no — you can open 4D and start building immediately. But developers who skip the theory tend to hit a wall once their databases grow beyond a few tables. Learning normalization and key design first saves significant rework later, and the concepts transfer to every other database you’ll ever touch.

Which 4D book should a complete beginner start with?

Inside 4th Dimension by Steve Hussey and Geoff Perlman is the most commonly recommended starting point. It covers most topics at a beginner-friendly pace. It was written for 4D 6.0, but the material remains very similar to 6.5 and later versions, so it’s still useful.

Is the 4D-NUG archive still worth searching?

Yes. It covers over eight years of developer discussions and contains solutions to problems that never made it into official documentation. It’s imperfect as a search tool, but with a bit of trial and error — and careful choice of search terms — it remains one of the most practical resources available.

What is Dimensions Magazine?

Dimensions was a bimonthly, 60-page technical journal for 4D users and developers, published for roughly eight years. It featured intermediate and advanced articles written by community members and ACI staff, and subscribers could receive an examples disk with the databases used in the articles.

Do I need to buy every book on this list?

No. Start with one beginner book and one theory book. Add Programming 4th Dimension once you’re building real applications, and consider 4D for Fun & Profit only if you’re planning to work commercially. The community archives are free and cover much of the same ground for specific problems.

How long does it take to become productive in 4D?

It depends heavily on your background. Developers with prior database experience often become productive within a few weeks; complete beginners typically need a few months of consistent practice. The biggest variable isn’t 4D itself — it’s how well you understand relational design before you start.