I have just posted a couple databases to our intranet using the web companion. Everything seems to work fine EXCEPT when you try to change any of the Data you get an error message, "Data Entry Error - Your attempt to save current record failed because of the following - Unknown error number 102"

As it is posted right now there are no passwords for either of the database,everyone can change everything. I have not changed the web layout, in fact after I enabled the sharing, I have not changed any of the "web" components from what the web companion set up originally.

Can anyone help?

I figured it out. It appears that you have to set passwords, even passwords that give full access. It was a pain that it did not say this when it was talking about passwords and security in the User's Guide. Thanks

Hi, here's the error code list, something that really should be in the manual!

You'll find that 102 is "field missing" - means it's not on the layout you're calling

jeff

FMP_error_codes.txt

Re: ... that really should be in the manual!

It comes shipped in FileMaker Help. Search for "Status(Current Error) function". Because it comes shipped, FMI might suggest that putting it in a manual would be redundant.

The Help menu and manual are a little deceiving on the error codes. "Status(Current Error) function" is great when that is how it displays the error, but when you are accessing your DB from the web it isn't worded that way. This causes a FM newbie like myself to be alittle uncertain, but I appreciate both of your help.

My problem now is how to fix this? I let filemaker web companion make the pages. Which is why "field is missing" didn't make too much sense. Maybe this is another way that the Web Companion makes publishing your database "easy"

I've noticed this problem when using IWP before. I couldn't quite pinpoint the problem, but I'll tell you what happened to me and how i fixed it.

I use IWP for one of my databases. I have buttons that go to different layouts. I have a main layout that has a certain number of fields. Another layout has other fields. On one layout when I tried to submit changes, I got the 102 error also. I couldn't understand why. So, I put the fields from my other layout onto the main layout and made then invisible and did not allow entry into these fields. In short, the problem went away.

Not sure if this will get rid of your problem, but it might be worth a shot.

Ken

I'll give it a try.

Thanks,

Liz