A historical collection of Visual Basic 6 examples for forms, controls, files, graphics, multimedia, networking, system information, and utilities.

This is a collection of mostly independent desktop examples, not one application. A folder name combines an example number with its subject, while 8实例92-100/ and 000_My set/ hold additional groups and assets.

The repository is not marked archived in GitHub metadata, but its Visual Basic 6 projects, controls, Flash material, and Windows integrations are historical. No shared package manager, supported OS, installer, or common entry point is declared.

The refreshed default-branch tree contains 397 files in 81 directories, including 72 top-level example or collection directories.

The counts show tracked material, not that every project loads or is safe on a current Windows system.

Folder labels describe intended demonstrations; they do not guarantee completeness, correctness, or current platform compatibility.

Each .vbp owns its adjacent .frm, .frx, .bas, .cls, control references, media, and data. Identically named forms in different directories are unrelated modules.

Open only a selected .vbp with a compatible Visual Basic 6 environment after reviewing its references. No verified IDE version, Windows version, build command, or registration procedure applies to the full archive.

Projects may rely on legacy OCX/ActiveX controls, Windows APIs, registry access, Flash, multimedia components, local files, or networking features. A missing control must be recorded for that project; do not register bundled binaries on a normal workstation merely to make a form load.

1. Select one example and inspect its .vbp references plus every form, module, class, resource, control, and data file.
2. Identify file writes, registry changes, launched processes, network access, system settings, required privileges, and cleanup.
3. Copy that complete project unit into an isolated compatibility environment; keep relative paths unchanged.
4. Load and build only after checking unknown binaries and controls, then test with synthetic data.
5. Record the exact environment, missing dependencies, observed output, side effects, and reset result.

There is no repository-wide run or build command. A procedure verified for one .vbp must not be applied to another project without a fresh review.

• Visual Basic 6 and legacy ActiveX controls may be unavailable or unsafe on current Windows versions.
• .frm, .vbp, and related metadata can use legacy encodings and serialized layouts; bulk formatting or UTF-8 conversion can corrupt them.
• .frx, .ocx, .oca, .exe, .swf, and other binary files must be treated as untrusted and kept byte-identical during documentation work.
• Examples can change files, the registry, the desktop, network settings, display state, or other host configuration.
• Chinese paths and control/resource filenames may be referenced from project metadata; renaming them can break loading.

No repository-wide test, build, lint, or format command was found. No .vbp was loaded, compiled, or executed during this documentation audit, and no OCX registration was attempted.

For a changed example, record the exact project, environment, resolved references, input, output, and side effects. A successful form load is not proof that behavior is correct and does not validate the other 80 projects.

Keep code changes within one project directory and preserve form serialization, control names, event signatures, encodings, and local assets. Avoid a shared launcher or bulk migration to another Visual Basic generation.

Keep English, Simplified Chinese, and Japanese READMEs aligned in section order, counts, paths, links, compatibility details, and safety warnings.

No repository license file is present. Source, controls, binaries, Flash content, icons, and media may have different origins. Confirm authorship and permission before reuse or redistribution, especially for third-party OCX files and compiled content.

• HaoXiang Huang
• Rays688888@Gmail.com
• Project homepage