| Author |
 Topic  |
|
|
Dan Martin
Average Member
USA
528 Posts |
 Posted - 15 July 2002 : 19:04:30
|
The latest beta version .81 of TableEditor does away with the need to touch the ASP to connect to the database. (This feature may have been around for a while...I don't watch it like a hawk.) Not only does it let you enter the location into a text field, it even provides a nifty browse feature that shows the remote system's directory tree.
From watching the posts, it seems that one of the most common hangups new users run in to is setting up the database. I think it would be a great addition to Snitz. And, since Tableeditor is GPL, and Snitz is GPL, seems to me there are no issues of snagging the code.
But there is one major problem as I'm sure some of you veterans are fired up and ready to pounce on me for. The issue is that Table editor comes with its own database (te_admin.mdb) that it expect to be in the same folder, where it places these connection configs to all the other databases you wish to connect to. In Snitz world, that's a security no-no. That is definitely a hangup, and I'm not sure there is a solution to it.
But, most of you are smarter than I am. I thought it might be worth to bring up and get some discussion in the hopes that one of you might know a way. Or, you can all tell me I'm crazy (I'm prepared). 
|
|
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
Posted - 15 July 2002 : 19:10:49
|
it has a flaw though. It won't let you browse above the webroot, so if your database is above the webroot(where it really should be), you are back to entering the path manually. It's a nice feature, but as you said, there still has to be a database setup upon initial install, which brings us to where we are already.
If people would read the existing instructions and put a little effort into it, they would not have any problems with the connection string. |
 |
|
|
Dan Martin
Average Member
USA
528 Posts |
Posted - 15 July 2002 : 19:16:53
|
No arguement there. But it is an unfortunate fact that people don't. 
|
|
|
|
pweighill
Junior Member
United Kingdom
453 Posts |
Posted - 16 July 2002 : 04:35:01
|
People who don't read this instructions also tend to leave their access database in the same directory as the asp files and also don't rename it, so it is very easy in such cases for others to download the whole database and find out the passwords.
|
|
|
|
alex042
Average Member
USA
631 Posts |
Posted - 16 July 2002 : 08:36:14
|
quote:
And, since Tableeditor is GPL, and Snitz is GPL, seems to me there are no issues of snagging the code.
This is a nice script that I've already been playing with, but if you use it, you need to be careful. Afterall, if someone can get access to this script from your site, it can be a huge security breach.
|
|
|
|
dayve
Forum Moderator
USA
5820 Posts |
Posted - 16 July 2002 : 11:25:04
|
I've been using the new table editor for about a month, but not for web projects, more for remote database access. I like the new features.
http://www.nineinchnailz.com |
|
|
|
Dan Martin
Average Member
USA
528 Posts |
Posted - 16 July 2002 : 11:35:06
|
quote:
This is a nice script that I've already been playing with, but if you use it, you need to be careful. Afterall, if someone can get access to this script from your site, it can be a huge security breach.
True, you have to be careful. You certainly should move the default te_admin.mdb file off of the webserver, and use careful passwords.
Well, okay, so there's no possibility of using this approach. Do you think if the database connection portion where moved out of config.asp and into it's own standalone file (which is in turn included in config.asp) it might be easier for people to follow the directions? I know when I first used Snitz, my ASP knoweledge was nearly non-existant (to Snitz's credit). Believe it or not even I found opening config.asp to be slightly intimidating.
|
|
|
|
alex042
Average Member
USA
631 Posts |
Posted - 16 July 2002 : 13:14:09
|
I don't know if spliting up the config.asp file for just the setup would be that beneficial.
|
|
|
|
Dan Martin
Average Member
USA
528 Posts |
Posted - 16 July 2002 : 14:20:47
|
If you split it out into a seperate file that's got nothing but the database connection information, say inc_db_connection.asp, you could do things such as:
- On the Snitz setup routine, if the database connection is not working, you have wizard that asks the user super-simplistic questions. (could even support a browse option like Table Editor)
- As a result of the answers builds the database connection information.
- Then builds the appropriate connection and asks the user to copy and paste it into inc_db_connection.asp.
I'm certainly not criticizing the way it is done now. Just thinking of ways that might make it easier for some people.
I also think a inc_db_connection.asp file with only 6 lines of code is more comfortable for those without ASP experience than a large file like config.asp, even with no wizard.
Edited by - Dan Martin on 16 July 2002 14:23:42 |
|
|
| |
Topic |
|
Topic Locked
