calling a new record when file is in preview mode

[mediarare]

Anyone else experince general weirdness when you call new record request from a file while it is in preview mode?

I'm not sure if this is a known issue, and having inherited this database I'm not responsible for having not made the print scripts leave the file they are printing enter back to browse mode before completing themselves. But now I'm making sure all the print scripts do this.

Been pulling my hair out for about a month on this one.

The thing is, the file that was being left in preview mode, was the basis for a relation that showed up in a portal where data was entered, not the file itself. I decided to not use the portal for entering data, and that's when I discovered the file was being left in preview mode.

[-Queue-]

You can't create a new record while in Preview Mode, nor would you want to as no data can be entered.

[mediarare]

yup, the situation this occured in was an invoice with line items where the report of the invoice is in the line items file and the printing script left the line items file in preview mode. All data was entered into the lineitems file via a portal in the invoice file, so detecting that the lineitems file was still in preview mode did not occur until I decided to do all data entry in the lineitems file itself.

It would be nice for filemaker to throw a message box when you try to create a new record in preview mode to know that you can't do it :

[-Queue-]

Ah, now I understand what you mean. Yes, that would be nice. It would be similar to warning that a file is in Find Mode while you're trying to access fields based on relationships to it, which it doesn't do either.

As a rule, always enter Browse Mode at the end of a preview script. It will make your life easier.

[Vaughan]

"It would be nice for filemaker to throw a message box when you try to create a new record in preview mode... "

If the new record process is scripted then YOU the developer can throw up the message, using the Status(CurrentMode) function. Or issue a Enter Browse Mode step just before New Record/Request to be on the safe side.

If the new record process is done manually... I don't want FMP throwing up alert dialogs each time a user does something stupid. It'd make scripting a nightmare.