Member Avatar for P.manidas

Dear Sir/Madam,

I have developed a software on game using VB 6.0 and Access, and I want to make that software as a Register Version. The software may ask the user for registration key at the time of installation or after specified period of time being installed.

I can make that software as ..
1) Software will ask for a registration key after 15 days (Specified Days) or after run/used by the user 15 times, keeping the value on database or in a control like textbox for comparing.

Here I want to know, will it be good practice to keep that comparing data on database or I have to keep that data somewhere else? Which will be the safe practice for future? If somewhere else how?

And I have no idea on how to make software which is asking for registration key at the time of installation. Please guide me.

Edited by P.manidas because: n/a
  • 3 Contributors
  • 5 Replies
  • 342 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by kinwang2009

Dani AI

Generated

A short, practical roadmap that builds on question and the suggestions from and .

A simple file or Access-table counter is the fastest way to get a 15-day / N-run trial working, and an installer or a first-run dialog will cover the “ask at install time” option. For production use, an installer engine (Inno Setup or the Windows Installer toolchain) is the right place to implement a registration step or to drop a verified license file during setup. Inno Setup | Windows Installer docs. (jrsoftware.org)

Storing the trial counter or a plaintext key inside the shipped Access database or a simple .DAT file is convenient but fragile: those artifacts are trivial to edit or delete. Treat any client-side storage as obfuscation, not protection. Sensitive licence state should be kept cryptographically protected and minimized where possible. See OWASP guidance on protecting data at rest and limiting what is stored locally. OWASP Cryptographic Storage Cheat Sheet. (cheatsheetseries.owasp.org)

A stronger, widely used pattern is server-side activation plus a signed offline license file: generate the license on a trusted server, sign it with the private key, ship a signed token or file to the client, and verify the signature with a public key embedded in the app. This supports offline activation and machine-binding while preventing local edits to expiry or feature flags. Never embed the private signing key in the client; follow key-management best practices. See an example licensing model and offline/signed-license workflow. Cryptolens: signed offline license / activation examples | OWASP Key Management guidance. (help.cryptolens.io)

Concrete checklist for a VB6 + Access game:

  • For a quick ship: implement a first-run prompt, store a small encrypted marker in ProgramData and one registry value (defense in depth), but accept it can be bypassed.
  • For robust protection: use an installer UI to collect the key, validate it against an activation server, and save a signed license file that the app verifies at startup.
  • For fully offline customers: generate a signed license file on an admin page and deliver it (USB/email); implement a reasonable offline grace period and a support path for hardware changes.
  • Protect private keys, rotate them if compromised, and keep license verification code easy to support for legitimate customers.

Nothing client-side is unbreakable, but combining installer-time key collection, signed license files, occasional server checks and good key handling gives a practical balance of security and user experience. (jrsoftware.org)

Recommended Answers

All 5 Replies

Member Avatar for kinwang2009

Hi P.manidas,
I think this should not give you headache since you can save your Registration Key in File (I recommend you not to save your registration Key in database if you don't know how to use encryption). When ever your software opens ask for Registration Key if they have not registered. You can also save how many times they have opened in a file format which VB can read.

Thankx

Member Avatar for vb5prgrmr

This subject has been covered many times over the years and as such, as search with your friends (yahoo, google, ask, answers, bing) should provide you with some results...

Now, as for requesting a registration key upon installation you have many different choices on how to do this. There is the setup package that comes with VB, the PDW, which is customizable but it is outdated. Then there is the update for it, Windows Installer 1.1 (see pined thread on tips and tricks to find the link to download it from an archive site), which you can also customized with downloads from M$. Search M$ for Windows Installer SDK. Then there is Inno, wise, and a few more out there.

NOTE: If you decide to make alterations to the Setup1.exe project (found where VB is installed), I suggest that you make two copies of it. One for backup, and one for alterations.

Now, if you don't want to go with the setup route, you can go an easier way and that is alterating your project so when it runs the first time it prompts for the registration key...

Good Luck

Member Avatar for kinwang2009

Hi P.manidas,
See my attached help I have made for you. In my example i have used .DAT file to save my Registration Key, with Number of times used and whether user have registered or not.

Use 1234567890 as Registration Key in my example.

Thankx

Making_Registered_Version.zip (2.98 KB)
Edited by kinwang2009 because: forgot to give registration key
Member Avatar for P.manidas

Dear all,

Thank you for guiding me in such a way which has given me some information in this subject.

Thank you.

Member Avatar for kinwang2009

Hi P.manidas,
If your thread is solved please mark it as resolved so that people who need similar help can view this thread and helpers will also not waste their time going through this thread.

thankx

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.