2/13/2008: New! QSale Information and News

[dhUser]

TimLight:

- To change the username and password:
Type ADM into the textbox (in the sales screen) and press [Enter] and the admin dialog will appear. Just change it and click [Close]

About the other comments, I'll see what i can do.

dhuser

[Dale Harris]

Transaction numbers are not a bonus but are absolutely required. I receive email about POS from all over the world and there is no place that will allow you to use any type of cash register / POS system that does not issue a sequential transaction number to each and every transaction including each sales / return receipt, opening / closing receipts, no sales, voids, and anything else that can be rung on the register.

Some countries require 4 digit rolling (9999 is followed bt 0000) transaction numbers. Some countries require 6 digit rolling transaction numbers. Some countries require a two part transaction number where the first part is the number of times the register has been closed the second part is the number of transactions since the register was last closed starting at one. For example 256-25 means that the register has been closed 255 times before and this is the 25th transaction since the register was last opened.

[Dukane]

dhUser,

How do I change the password permanently? I was able to change it for one session, but when I closed the program, it didn't remember my change.

And, why doesn't the close button kill the application? I found it running 2 hours later when I thought I had terminated it.

[dhUser]

TimLight,
- In this version, it is unable to save the password. This will be corrected.

- To end the application completly, type X in the main screen's textbox or logout and press cancel.

dhuser

[Dukane]

Why don't you save the passwords and transaction numbers in binary files?

[dhUser]

TimLight,
How would I do this, with Visual Basic 2005 Express Edition?

dhuser

[Dukane]

Well here is an example of a quick way to write to a binary file:

Code: Select all

Imports System.IO

Private Sub SavePassword()
            Dim newPassword As String
            newPassword = Console.ReadLine()

            Dim DataStream As New FileStream("password.pwd", FileMode.Open)
            Dim PasswordWriter As New BinaryWriter(DataStream)

            PasswordWriter.Write(newPassword)

            PasswordWriter.Close()
            DataStream.Close()
End Sub

It's certainly not fool-proof since anyone who has programming knowledge could simply write a program to open the file and read the password out. But it prevents anyone who doesn't know how to do so from doing just that -- and prevents someone from "finding" the password file and opening it and simply reading it out as straight text.[/code]

[Andrew]

I'm glad to see VB.net has not improved... [shudder]

[Dukane]

Andrew,

HAHA guess not. Although I should add the disclaimer that the code above is for 2003. I'm assuming it will also work in 2005.

[dhUser]

This is how I will do the username and password:

Edited out for security purposes

dhuser

[Dukane]

But you just made it public.

[ChrisKraus]

Ouch

[Andrew]

*hugs PHP's easy, built in string encryption*

[ZeeMan]

Why not use a keyed encryption algorithim that stores the values in the registry?
I haven't used VB express 2005 for a while so here is some psudo code (it isn't very good):

On New Password:
Users enters new password.
Store new password in var newPass
Set var toEncode to var newPass
Set var encodeKey to var newPass
Encode var toEncode with encodeKey

On Logon:
User enters password.
Store password in var enteredPass
Store password in var decodeKey
Decode encoded password with decodeKey
Does entered password match decoded password?
If yes:
Open Program
If no:
Display Error

It isn't very clear but you get the meaning. This way, the only way to decode the password is to know the password.
You don't have to use any advanced encryption algorithim either. One little experiment program I wrote just converted the key and value to encode to ascii and then multiplied them by each other. Another method could be to multiply the key by some really long number that you keep a secret. As long as that number is not comprimised, you are fine.
Yet another way to encode the key is use a really complicated algorithim that does a bunch of functions using several keys that are kept a secret. Then, if somebody tries to crack the password, they don't know how long the password really is or how it was encoded.


These are just a few suggestions.

[listerofsmeg]

I can dont get to the site!

Can you host it on a file host!
PLEASE.
also, is it a EXE or still VB code?