Would you be trying to access records by "RecordNumber" and not "RecordID". This has caused a similar problem for me in the past.

All the best.

Garry

One of my colleagues came to me with what seems to be a peculiar problem using instant web publishing. I tried everything I could think of, to no avail. I've never used the instant web publishing though, so hopefully I've missed something simple/obvious. Any and all help is appreciated.

Here's the problem,

My colleague is sharing a single flat file using instant web publishing. Some records were entered before the file was put up on the web and some after. Using the password set to allow creation/editing, he can edit the older records but not new ones. He can create new records but cannot subsequently edit them. To make things even more perplexing, another colleague, located at another location, can edit everything using the same password.

Here are the details I gathered:

The file is being hosted on a PC using Filemaker 5

Both colleagues are using Internet Explorer on PCs. (We tried it on IE on a MAC and on another PC and were not able to edit the newer records.)

The passwords appear to be set up correctly and editing works fine when the database is accessed directly.

Using port 591.

We tried disabling and reenabling the file. With no luck.

Thanks in advance,

Jenni

Thanks for the thought, but I don't think that's it.

They're using the built in search in instant web publishing. They have no problem locating the records they wish to edit. They simply cannot edit them. The hand icon will not change to an edit icon.

Maybe a browser problem? Do you have IE 5 on both machines?

Check if any access privileges/passwords have be defined in the database. It sounds like some record-level security has been setup.

Thanks to all who've responded thus far.

Some further investigation revealed that the presenting problem was actually a symptom of a different problem. As it turns out, when any user navigates to a record from the list view, they can edit the record. When a search is used to locate the record, however, the user cannot subsequently edit it.

Does this shed any new light?

Thanks

Perhaps the problem is that IWP is wysiwyg.

If you (or your colleagues) will learn html/cdml you (or your colleagues) can do custom web publishing which will allow you (or your colleagues) control of the site.

Hmm...if my automatic is stuck in second, I suppose I could bypass the problem by buying a stick shift.

We're not trying to do any thing fancy. Searching for records and editing them are clearly within IWP's intended opererations. If anyone has any further helpful suggestions for solving this bug, I'd appreciate hearing them.

Thanks,

Jennifer Weiss

MIT

Or you could learn how to repair your auto-tranny. Just like you could learn custom web publishing so that you could have control where IWP leaves you wanting.

You're welcome.