Gossamer Forum
Home : Products : DBMan : Installation :

modification problem

Quote Reply
modification problem
I've installed DBMAn about 6 times for my school district with great success.

I usually use JP Deni's configurator to set things up. It has recently come to may attention that 3 of the scripts will not modify records.

When I go in with admin rights, search for the record to be modified, click on the radio button and click Modify I get bounced back to the Modify a Record screen. When I try to modify from there it tells me that it can't find records I know are there.

Where should I start looking to trouble-shoot this problem?

Thanks

Quote Reply
Re: modification problem In reply to
It sounds like a key value problem to me.

Are you sure that the $db_key field is set correctly?


Quote Reply
Re: modification problem In reply to
Thanks!! That fixed one piece of it. There was a communication problem and the people inputting data didn't put unique values in that field.

However, now when I go to modify I get an error message that says:

Error: Unable to Modify Record
There were problems modifying the record:

* User (Can not be left blank)
* Public Address (Can not be left blank)
* Private Address (Invalid format)
* Public Subnet Range (Can not be left blank)
* Private Subnet Range (Can not be left blank)
* Private Subnet Mask (Can not be left blank)
* Additional Information (Can not be left blank)

This happens even when I have put data in each of those fields. Any ideas??

Thank you very much for the help you've already supplied.

Quote Reply
Re: modification problem In reply to
Those errors means that those fields are required and you need to edit those fields in order for the modification to be submitted.

Regards,

Eliot Lee
Anthro TECH, L.L.C
Web: http://www.anthrotech.com/
Quote Reply
Re: modification problem In reply to
Are you sure that all of your field names are correct in your sub html_record_form? When you get the error page, are the fields filled in?


JPD
Quote Reply
Re: modification problem In reply to
You were right about that, too. This was a case of too many chefs. Our tech resource person had modified the fields without telling me and had accidentally named two fields identically. Woops!!