curly
Full Member
Posts: 161
|
Post by curly on Jul 5, 2021 3:29:59 GMT -5
Hi Rod and Brandon, Thank you both so much. Let me clarify that I understand. I will create a window to hold a textbox instead of the text editor to enable automatic wrapping. Each defect found will be stored in an array, (already exists as Defects$(100)). Each time a new defect is found, it is added to the array, the window and textbox 'showed', and ALL the defects in the array printed to the textbox overwriting what was already there? I will include a button to hide the window.
I assume from Brandon's code that I will need to use a CR and LF at the end of each defect to force each defect to a new line?
One other quick question, can I use a 'tab' character ( chr$(9) ) in the defect description to create some vertical alignment?
Re Brandons comment on the possible number of different defect descriptions, it has taken much more code to validate the data thatn to collect, display, manipulate and store it. I initially hard coded the defect descriptions because each initially appeared to apply to a specific scenario, but have decided to store them in a .dll file that can be edited without messing with the programme going forward? For the record, all the reference data I use is stored as .dll files so they can be edited easily - is that the right way?
Thanks again, be back soon, I'm sure.
|
|
|
Post by Brandon Parker on Jul 5, 2021 7:51:09 GMT -5
I would definitely use a CFLF pair after each line item. Maybe even two since you might want to draw some distinction between the separate ones. You can most certainly use chr$(9) within a TextBox. What do you mean when you say you are storing the information in a .DLL file? You are creating Dynamic Link Libraries for storing information? A simple .DAT file would suffice for that purpose. That being said, it would be kind of insecure and someone could accidentally change data (of course, someone could accidentally delete the entire program as well... ). There are definitely standards for storing data, but you will find that often people use what works and what they are comfortable with. {:0) Brandon Parker
|
|
curly
Full Member
Posts: 161
|
Post by curly on Jul 5, 2021 8:48:08 GMT -5
Hi Brandon, Thank you again,
Please don't tell anyone 'cause it's secret, but my reference data files resemble CSVs in format, but I have used a strange symbol in place of a comma, and then use my own encryption to change every character in the file. This allows me to use commas in my data strings, and somebody would need to know the encrypted symbol used in place of a comma to read the file, and then try to unravel my encryption to decypher the data? I use a short filename with .dll extention to create more confusion! I've written a small utility programme to unravel the data files so I can edit them. I use information provided by you earlier to check the existance of the data files before I open them. I would like to find a way to prove they are not correupted as I read them in, but that's on the back burner.
I have assumed you all live in a sunshine state somewhere where it is warm all the time? We get cold winters, and people keep adding thermal insulation to lofts and end up totally enclosing electrical circuit cables in thermal insulation in their lofts. This has a dramatic effect on the current carrying capacity of the cables, and can results in acute fire risks. I thought you would like to know that!
|
|
|
Post by Rod on Jul 5, 2021 9:48:30 GMT -5
My only thought that I can add to Brandon’s comments is that .dll are system files and may be treated with suspicion by virus checkers. .dat and .txt are less suspicious. Some virus checkers and mail systems get upset by .bas so I would change to something less contentious.
|
|
curly
Full Member
Posts: 161
|
Post by curly on Jul 6, 2021 2:34:50 GMT -5
Thanks Rod, I'll keep the encryption and use .dat as the file extension from now on to avoid such issues.
I'm sure I'll be back soon
|
|