This topic is locked

Questions and Feature Suggestions

6/4/2003 9:49:27 AM
ASPRunnerPro General questions
author

We like the simplicity of the product and speed is excellent. However, it still appears too limiting for corporate use. Answering the following question would help our evaluation. I am very experienced at ASP, ADO and database againt MS SQL Server.

  1. We want to create pages for mainting several tables in a single database. However, each time we choose to build against a new table, it over-writes the previous files with the new information. Yes, we can move the files out so they are not over-written but does that we mean I have to go manually move the last set of generated pages, then attempt to merge all of your code into a single set of files? Using a different virtual directory for each table to edit is unacceptable. Is it possible to create code that will permit editing of mulitple tables? This is the single most major issue we have with the product. Perhaps you can show what I am missing or how to get around this even if it required manually editing.
  2. Why do I have to choose a key field editing to get it to appear on an "add" form? During edit, the primary key should not be edited so should not this be saved in a hidden field? Currently, one must make a primary key field editable during an "edit" just to get it to appear in an "add" form where it is a must.
  3. Usability. While I appreciate your desire to keep ASPRunnner simple, most users would appreciate the following simple features:
    A) Ability to save basic information such as sql server connection string (at least the server name I typed in).
    <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=question&id=84&image=1&table=forumtopics' class='bbc_emoticon' alt='B)' /> Ability to save the answers to the generation wizard so you could regen without reanswering every single option from again and again.
    C) Ability to create ddlb with query into separate table (lookups) (I believe you plan to add this to a future release).
    D) On your popup calendar, dynamically change the window name on each call using time or another dynamic value. This would force a new window appear each click. Currently, the calendar window is overlayed by another browser window, the click on the calendar icon appear to do nothing because the browser is not smart enough to bring that already opened window the top. Another options are to use a "modal" window or to inline frames if the browser is later version of IE.
    Look forward to your reply.
    Don

    don@draperconsulting.com

D
dlguild 6/5/2003

I agree totally, particularly with paragraph 1. We currently have all our database update functions in a password protected folder, with the 'default.asp' file as a menu tree to the various updates. Because your database connection routine uses a single database connection variable, rather than one customized for each database to be updated, all the generated code has to either reside in separate sub-folders, or all the code has to be modified to use a unified dbconnection.asp file. Same is true for the login.asp page.