Jump to content

Unknown error number -50 (continued)


This topic is 8422 days old. Please don't post here. Open a new topic instead.

Recommended Posts

The problem is still happening after upgrading Web Companion to v6.

"Submit" will work if I have not used the search function. But if I use the search on any of the fields, the error occurs (after doing the edit, modification and then submit)...

Any leads would greatly help!

Link to comment
Share on other sites

quote:

Originally posted by mf:

The problem is still happening after upgrading Web Companion to v6.

"Submit" will work if I have not used the search function. But if I use the search on any of the fields, the error occurs (after doing the edit, modification and then submit)...

Any leads would greatly help!

What do you mean by "doing the edit, modification and then submit"?

You can submit the new record, or Modification of Record. Not Edit/Modification and then Submit.

Link to comment
Share on other sites

If you check the posting of June 11th, I thought that the issue was becasue I did not have the most recent version of WC. But after doing the upgrade, the problem persists.

This is how it goes:

1. Do a search on, say a department, to obtain all the products of that department.

2. Go back to Form view and edit the first record.

3. When I choose "Submit record", the error message appears.

4. When I clear the error message, I am back in edit mode, and I need to click "Back" to exit from the edit mode. No change has taken place.

If I simply show all the records (no search) and edit a record, the "submit record" goes without a glitch.

Any help is welcome at this point... it is a bit of a desperate situation here.

Link to comment
Share on other sites

just so i'm/we're getting you straight.....(u use different termanology to me I think!)

You do a find all on a department name -- works OK

you then click on a record detail link (either URL or form button) to "bring" that particular record into a format file that contains a form with an -Edit action -- (I assume this is what you do) works OK?

you make your changes to that record by changing the information in 1 or more text / text area fields -- OK

you click the submit button with the -Edit action on it. -- you get an error (-50).

I personally think from what you say the error resides somewhere in your database setup but its hard to say without seeing it in action and looking at the format files....

[ June 16, 2001: Message edited by: scratchmalogicalwax ]

Link to comment
Share on other sites

quote:

Originally posted by mf:

This is how it goes:

1. Do a search on, say a department, to obtain all the products of that department.

2. Go back to Form view and edit the first record.

3. When I choose "Submit record", the error message appears.

4. When I clear the error message, I am back in edit mode, and I need to click "Back" to exit from the edit mode. No change has taken place.

If I simply show all the records (no search) and edit a record, the "submit record" goes without a glitch.

Any help is welcome at this point... it is a bit of a desperate situation here.

I like to help you, but I don't understand singe point after the number 1.

Link to comment
Share on other sites

What if you do a search and then an -Edit and the portal fields are populated do you get an error?

Do you -Edit any of the fields involved in the relationship between the databases when you do the -Edit?

Are you trying to -Edit potal records and "native" records at the same time?

from your description it's not obvious from where i'm sitting exactly where the error is coming from (without making assumptions which won't help you)......I would bet on DB/relationship incorrectly setup in some way but that don't help you much does it!

You could try the backward engineering approach to try to isolate the error to a specific relatinship / field setup by breaking the application down to it's constituant parts and rebuilding it bit by bit.

That is the only way you will find it i think.

It's all good "fun" and you'll learn a lot from it

laugh.gif" border="0

Link to comment
Share on other sites

Thanks,

To answer your questions:

- Right now I am not even touching the portal records. I am simply entering the word "test" in a field in the main record.

- And yes, if the portal records are populated, there is no error.

And I have been dismantling the thing for a few days already...

- making the formating as simple as possible

- removing fields that are not needed for the test

- redefining the relationship with the related file (removing sort for example)

I'll keep trying (it has to work right?)

frown.gif" border="0

Link to comment
Share on other sites

Back to basics: are you using Instant or Custom web publishing?

When you use the browser's back button, be sure to click the refresh/reload button, otherwise (especially with MIE) you'll only see the cached data -- what the page previously was. Any attempts to perform further work on the cached page might cause errors, because the record in the database has changed or might even be deleted!

(Anybody old enough to remember the 68020/040 cache problems? Heh heh, it's back to haunt us on the web!)

Link to comment
Share on other sites

All right,

I wish I could demonstrate... but I will try again to explain the sequence of things.

I am simply trying to save a change to a record using Web Companion.

The problem does not happen all the time; 2 cases cause the error to show up:

1. If a do a search before editing a record, the error -50 shows up. Otherwise, if I simply select a record with its record number, edit it, the save is accepted ("submit" works).

2. If the portal is empty (no related records), the error -50 shows up... If there are related records, no problem.

Since I have posted this last week I have also found out:

1. Installing WC 6 does not make a difference

2. Recover does not help

I think I have isolated the problem: it is with the portal: if all the fields from the portal are "read-only" (do not allow entry into field) it works.

Keeping the portal "read-only" is not really a solution since we need to make changes to these records too.

Can anyone suggest a work-around?

Link to comment
Share on other sites

quote:

Originally posted by Vaughan:

(Anybody old enough to remember the 68020/040 cache problems? Heh heh, it's back to haunt us on the web!)

How about my Apple IIe problems?

Really, there were none as far I can remember. I was using AppleDOS, Pascal and CP/M running on Z80 Microsoft HW Card. Microsoft was just small company doing additional HW for 1 billion-dollar company Apple Computer. Great stuff!

Link to comment
Share on other sites

Here I am again...

We are using Web Companion v6 (vanilla). I have customised the form view. I have used the refresh with no change in the results.

The latest I have tried was to recover all the files into a different folder, open the recovered files to export the data into tab files, clone the recovered files into yet another folder and import the data back. Results: no change...

Am I just dreaming? Can portal records be edited using Web Companion?

Thanks for any ideas you care to send my way.

p.s. The database works great when accessed directly via the server (by the majority of the users) so I am reluctant to make any drastic changes to the database (particularly the relationships).

mf

[ June 22, 2001: Message edited by: mf ]

Link to comment
Share on other sites

RE: Am I just dreaming? Can portal records be edited using Web Companion?

When I am editing portal records e.g. lines in order in e-commerce, I am editing directly the record in the portal file. Not through the portal itself.

Couldn't you try CDML this way?

Link to comment
Share on other sites

After much trial and error, I am now successfully creating 'native' records and 'portal' records with one -add action, and editing the same records with one -edit action.

quote:

Originally posted by mf:

1. If a do a search before editing a record, the error -50 shows up. Otherwise, if I simply select a record with its record number, edit it, the save is accepted ("submit" works).


1) Make sure the portal records are on the layout called up by the search string. In my experieince, you must name the layout when editing portal records, and the records have to be in the portal area on the layout.

2) What database are you in following the search? If your search string goes directly to the Portal db, and you end up with Portal db results, you can't use the same -db and CDML field coding as you would for results based on a search of your 'Native' db. (I hope this makes sense..its an awkward concept to describe).

quote:

2. If the portal is empty (no related records), the error -50 shows up... If there are related records, no problem.


I'll try to be brief in explaining the problem I had, and how my experience may apply here.

In my system, the relationship is based on matching an auto-entry field in NativeDB to a field in PortalDB. With usual html coding for an -add action, and at least one input field for the portal

(i.e., <input type=hidden name=PortalRelationshipName::SomePortalField.0 value="Whatever"> ), I successfully creat records in NativeDB and PortalDB, with the linking serial number automatically recorded in both dbs (I'm not sure why this works smile.gif" border="0

I wanted to validate entries in the Portal records, and set the FileMaker validation for some PortalDB fields to 'Not empty'. An error message was returned if these portal fields were empty on submit. Now the strange part...each time I got an error message returned on my -add, the serial number 'ticked up' in NativeDB, but no record was created, and PortalDB created a 'ghost record'. If #5 was the last record in NativeDB, and I fixed 3 error messages, I ended up with records #6, #7, #8 and #9 in PortalDB, and NativeDB 'jumped' from record #5 to #9.

Maybe the cause of your problem is similar. If you have fields in portal db validated by FMPro, you could get an error message on your -edit, and not have anything updated in your 'Native' db. Just a theory, but worth exploring.

One more thing: Remember to identify the number of the portal record being updated. Input fields on my -edit pages look something like:

<input name="Relationship::PortalField.1" value="[FMP-field:Relationship::PortalField]" size="22"> And don't ask me why the value doesn't include the portal row number...it won't display the current values if I include the row number. If you know why, please tell me!

wink.gif" border="0

Sorry this is so longggggggg.....

Link to comment
Share on other sites

This topic is 8422 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.