Question about encryption/creating aex

[Peter.Greulich]

Protection

It looks as if creating a master password requires using Alpha's built-in login routines. We have our own, which ties into our own permissions system. It appears that we'll have to use the encrypt() functions in code wherever needed. Is this correct? If so, we don't really mind, but more exact knowledge could save us some hours of keyboard pounding.

I encrypt tables but use my own login system. I set a master password in the autoexec script. If someone were to get into the system and delete the autoexec, they wouldn't have access to the critical tables since they would remain encrypted. If you roll your own, you will need to encrypt the tabels manually in xbasic.

Peter

[Peter.Greulich]

I just worry about my security being disabled by deletion from the control panel/code and the autoexec script being deleted so as to allow for someone to not have to purchase my product.

See my other response below.

[Mike Thomson]

Finian,

Suggest you check code archive - the attachment is a ghost!
Perhaps the import to the new Forum system

Mike

[Finian Lennon]

Thanks, Mike I didn't notice that the file was missing. It's there now.

Finian

[martinwcole]

here is a script Steve posted on the phoroum a few months ago:

it is assumed you have saved to a text file all your scripts and functions
(in the code tab, right click and select "Export" - later you can right click and select "Import" and copy them back) I don't use this on my development copy, only the finished copy to the client.

response=ui_msg_box("Caution","You, about to remove all scripts and functions - Continue?",276)
if response <> 6
end
end if

'if you haven't already made an AEX
response=ui_msg_box("","Make make aex?",276)
if response = 6
a5_compile_scripts() ' makes the AEX
end if

' Make and add new table to db
file.copy("your database name goes here.alb", "aex.dbf")
file.copy("your database name goes here.alm", "aex.fpt")
file.copy("your database name goes here.alx", "aex.cdx")
file_add_to_db("AEX.dbf")

' Remove scrips and UDFs
t = table.open("AEX")
filter = "type = 'scrp' .or. type = 'gudf'"
t.delete_range(filter)
t.pack()
t.close()

' Replace al* files with new dictionary
file.copy("aex.dbf", "your database name goes here.alb")
file.copy("aex.fpt", "your database name goes here.alm")
file.copy("aex.cdx", "your database name goes here.alx")

' Erase temp table
table.erase("aex", .t.)

[Kevin G. Timberlake]

Dazed and Confused

Ok...I created the .AEX and deleted all my scripts, menu's, toolbars, and functions. Restarted A5...no more menu's, toolbars, or Navigation bars. What am I doing wrong?

[Kevin G. Timberlake]

Got it. Delete only the scripts and functions. Leave images and toolbars/menus intact.

[Finian Lennon]

I was worried there for a moment that maybe you'd wiped yourself out!

I'm going to
(1) Library containing "regular" scripts and functions
(2) Library with menus and toolbars
(3) Library with "custom" scripts, a workaround to keep indivually customized installations intact during future automatic upgrades
(4) Library for script fixes ... I have an Xdialog that displays the contents of this library. The user can run any of the scripts from the xdialog. If something turns up post release, I can copy over the fix and have the user run it.

I keep nothing (almost) besides the autoexec in the database library.

Finian

[CALocklin]

Finian, are you saying that you are moving away from aex files in favor of .al* libraries?

[Finian Lennon]

In my mind aex and alb are synonymous though in reality, of course, they are not.

No, I'll be using four compiled aex files going forward.

F.

[Kevin G. Timberlake]

Wiped out??? Me?? Oh man I learned in the begining, I have 3 backups of each db.
1)Development
2)Distribution
3)Backup of Development before changes made

I am now getting the .aex proceedures down. Moving slow, but forward.:)

[Finian Lennon]

Sounds sensible to me.

F.

[Kevin G. Timberlake]

Hmm.....I created the .aex, kept the images, menu's and toolbars in the code section of my db. But now some of my custom scripts do not work. Any advice?

[Finian Lennon]

Until you're satisfied that everything is working you should keep the full library available in the application folder. When you find a problem, you can then File/Database/Properties and add the library back, drop the aex and then debug the script. I've never encountered a script that runs in the library and not in the aex.

Finian

[Kevin G. Timberlake]

:o Thanks. I found my bug. I needed to make sure when I transfered the db to another folder, I included the .aex. I did this and all worked well.