2/13/2008: New! QSale Information and News
Moderators:daleadmin, Dale Harris, Alan, Andrew
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
- 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
- Forum Owner
- Posts:1171
- Joined:Sun Dec 28, 2003 10:19 pm
- Location:Chicago
- Contact:
Transaction numbers
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.
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.
Dale
Well here is an example of a quick way to write to a binary file:
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]
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
- ChrisKraus
- Forum Regular
- Posts:351
- Joined:Wed Dec 31, 2003 11:10 am
- Location:Dedham, MA - U.S.A.
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):
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.
I haven't used VB express 2005 for a while so here is some psudo code (it isn't very good):
It isn't very clear but you get the meaning. This way, the only way to decode the password is to know the password.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
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.
-
- Forum Regular
- Posts:21
- Joined:Fri Jun 16, 2006 6:12 am
Who is online
Users browsing this forum: No registered users and 245 guests