we have been able to recreate a crash on our windows boxes that has me worried. on a date field with no field-level validation, if you enter an invalid date and click revert on the resulting dialog box it crashes and gives you a DLL error. you have to force quit FM. this is only happening on one table, but it seems to be on all the date fields in that table. it also doesn't happen on any of our macs, even the same field.

here are our operating specs:

--OS's affected: Win98, WinME, Win95; no problems on MacOS 8.5 or 9.x; didn't test Win2k

--error: MSVCRT.DLL error

--Bound file served through FileMaker Server 5.5, served on Win2k professional. The bound file has not been 'stripped' of it's backend

--it's not 100% of the time, but every 3rd or 4th attempt at reverting an invalid date.

any ideas? thanks.

jodin

Try it with an un-bound file.

okay, we weren't able to track it down and it just bit us in the *** the bug popped up and just about took the whole table with it. of course this is one of the largest and most used tables in our solution, and of course this happened while doing a customer install :-(.

here's what we know at this point (and we will do more testing today):

**happens in bound files (plain bound or stripped), 5.5 files bound with 5.0. we haven't received our full Dev5.5 yet to test with that

**seems to only happen on one layout. when we tested it on our 'dev' layouts we couldn't recreate it

**the initial error is on the 'revert field' dialog for an invalid date, after a restore of the file the field can't take any data at all without the crash.

**each crash now requires a restore

**this one happened in Win98. we've got it to occur in Win95, 98 & Me.

**doesn't occur in Win2k

At this point i'm thinking we will rebuild the layout that the error occurs on, investigate cleaning up our table (maybe save a clone then import into it, i don't know yet) and then send out the clean file. luckily the customer has an understanding IT guy and our file has an accessible import script.

live and learn, live and learn......

jodin

Update: we were able to squash the little bugger. I don't know exactly what it was, but a export, save as clone, rebuild the layout affected and check all relationships that touched the bad fields, then import and bind under Dev5.5 seems to have fixed the problem.

sorry i don't have more info on what it was, but it's gone now (hopefully forever!).

jodin