Hi.

We have a number of databases with many drop down boxes with differing value lists. On the client computer they work fine , however when we publish them using Instant Web Publishing and access them via our Intranet , the pop down menus appear however we can not choose any values. Also none of our edit boxes (for entering simple text) will not work.

Edited January 9, 200818 yr by Guest

There are several things here, if you somehow should have more than one file in the solution, should all files be shared not just the interface. Then is the interaction a modal one, where you enter data in the field and hit submit afterwards.

--sd

the interaction is a drop down menu..? nothing to enter just click the arrow and a list of values appear to choose...

the other interaction would be just entering text into the box and then yes, clicking submit at the end of all entry...

i'm not 100% sure if this is what you mean, as i am a very big NOVICE! thanks though..

(in my original post , by many databases, i mean that we have a few that are not and do not need to be connected... they are all seperate but are all having the same issue.... sorry i didnt make this more clear before)

Edited January 9, 200818 yr by Guest

We are also experiencing the same problem. the client works fine for data entry, but once I log onto the web, none of the fields will allow for data entry. They seem "locked". If I click around long enough, the fields will then become active, but it's frustrating a lot of users. Any suggestions?

Hi, I have just created a customer database (using the ClientTracker template) and am experiencing the same issue with drop-down menus when published through IWP.

Some drop downs work, others don't and yet they are all configured in the same way.

Does anyone have a solution to this yet?

Regards,

Drew

Hi again,

Just realised, after playing around with the layout of the database, that where there are drop-down menus, there are actually two field. One, for example, is filled with the company name and sits in front. The other is filled with what must be a a serial number assigned to that company to link the details all the way through.

Obviously having two fields on top of one another is never going to convert properly into HTML.

Any advice on how to get around this issue?

Drew