Keys and Indicies

You MUST have a proper populated primary key field to edit data.
This primary key field don't have to appear on any page. Make sure it exists in SQL query then proceed to Choose fields screen and remove this field from pages where you don't want to see it.

You MUST have a proper populated primary key field to edit data.

Thank you for your prompt reply, it's appreciated.
The only question remaining is why in a few cases do I not have Add/Edit capabilities on child tables? I've gone through every screen "very carefully" and made sure that everything was in order.
I verified that the keys (PK and IDX values) are indeed fully populated. I thought perhaps it had something to do with my security setup, so I removed them all (just in testing stage anyway).
Still no Add/Edit for certain children.
Since I'm in the begginning/testing stage, I'll just restart the project. Perhaps something got clicked along the way and something got lost in a dialog somewhere.
I'll post results.
Again, thanks.

Edit/Add pages can be enabled on Choose pages screen.

Edit/Add pages can be enabled on Choose pages screen.

Thanks admin. I did that. Now I get this error when I just try to access the test build:
Error Type:

ADODB.Stream (0x800A0BBA)

File could not be opened.

/aspr/libs/smarty.asp, line 182
I've checked the web and all indications are that permissions are wrong. I've got the IUSR (internet guest acct), and anon with RWED perms on the root of the test site and replicated to every directory.
I checked the sparty.asp file's perms and they are REWD as well and the DOS type file attribute READ is cleared.
Also, in IISadmin, I've given the root dir RW perms as well and the application is set to Medium Pooled (which is usuall sufficient).
Any ideas?
Thanks.

I would suggest to publish your application to Demo Account (last screen in ASPRunnerPro) and send the URL to support@xlinesoft.com.
This way we can see if there is anything wrong with the application itself or with your web server configuration.

I would suggest to publish your application to Demo Account (last screen in ASPRunnerPro) and send the URL to support@xlinesoft.com.

Hi admin. I worked on this for about 4 hours last night and several hours this am.
Here's what we did to try to resolve it:

1. Nothing we did worked, so we rebuilt the project from scrap and I used all the ASPrunner default settings. In other words, chaned nothing not even formatting,
   
2. Once we confirmed that everything workd, Add/Edit/List etc, we began adding changes as follows:
   
   [indent]a- Change Theme from default to: Madrid, Color: Madrid. Tested - all worked as expected,
   
   b- Started to apply Formatting characteristics, Email, Date etc. Tested all worked fine,
   
   c- Addedd code snippets to convert Text Fields to Ucase and Pcase etc. Tested - all worked,[/indent]
   
3. Decided I wanted to change the order of data on a list page. Went back to the appropriate page, made the change; then onto Visual Editor. It yelled at me that some settings...
   
4. I reset that page, rebuilt and tested. All of a sudden, that page reverted to Default Theme and Colors, the others retained my choices. In other words our test site now uses two different themes and we didn't tell it to do so,
   
5. I went back and reset that particular page again, rebuilt, now I get Smarty Errors Again.
   Also, we've tried to use code directly from your website (How To and Demo) such as:
   
   Uppercase in DB
   
   a) Goto Table Events -> Add/Copy/Edit -> BEFORE RECORD UPDATE -> Custom Code
   b)UpperCase: dict("FIELDANEM") = UCase(dict("FIELDANEM")), example Account_ID. OR Lcase for Lower Case
   Doesn't work. This of course causes us concerns. Aslo, once we reset a page, all our custom code disappears.
   I appreciate that we could publish to Demo Account and all, but at this point we are getting very frustrated. We get it working, make some cosmetic or functional changes, field order changes and it blows up.
   One of my roles (as well as two of my people) is to evaluate RAD software for clients. We are evaluating four products for two client that number around 120 users. Quite frankly we were very excited about ASPrunner, ease of use, flexibility and some other nice features.
   We are going to nuke this sample project one more time and rebuild - Yet Again.
   If we continue to run into these probems, I will have one of my people publish to demo site and we will move onto the next product to evaluate.
   We would think that after three people working on three different evaluation projects using this product that we would have some level of confidence and success.
   If we leave things alone from the original build all seems to be fine. In other words, if we make every change and configure every setting the first time around, all works.
   Please do not get me wrong. I certainly am not yelling or screaming, but are we are very frustrated and dissapointed.
   I (or one one of my people) will post results of this final evaluation test and result to demo account.
   I do want to thank you for all your assistance to date, it has been most helpful and is appreciated.
   We have also found some very usedful help and pointers on this site.

Wanda,
I'm sorry about your frustration.
A general advise - don't try to change all things at once. If you encounter something that doesn't work as expected publish your application to Demo Account and contact support team at support@xlinesoft.com.
This way we can what went wrong and help you fix this.

Wanda,

Thanks admin. We just finished a meeting and came up with the same thought. So here's our plan. We are going to completely wipe out everything, re-install and start from scratch. We have 3 client evaluation projects, so we are all going to work "indipendantly" on each of them (i.e. no colaboration). Should we each/any find difficutlies, we will document and post. Also, we are all going to review every piece of documentation, examples and demos.
We suspect that will help.
I believe that we did find one problem, it seems to be a multi-level sort (AcctNo, AcctName, Date). We removed this and the Smarty Error went away. As for the Themes - who knows.
We are using the eval version from the web-site, I don't suspect there are any limitations?
Anyway, again I want to re-iterate that I don't mean to be a complainer or otherwise suggest that this product is error prone. On the contrary, we've had some good success and hopefully we can move along.
Cheers for now.