I have been experiencing a problem on and off for a while and am hoping someone could help. We have 3 computers utilizing seedcode calendar and the host computer is able to start up FM/seedcode without issue. When the other computers open the database remotely, about 20-30% of the time the program crashes and I get the following error:

AppName: filemaker pro.exe AppVer: 11.0.3.312
ModName: msvcr90.dll
ModVer: 9.0.30729.6161 Offset: 0006ccd5

When this error occurs, you cannot immediately try again becasue the user remains logged in, so you must wait a few minutes. This can occur anywhere from just once, to 4 or 5 times in a row before success. I feel that I should also note that when the file is succesfully opened, the top bar of the window that reads "SeedCodeComplete" flashes between blue and grey about 3 times. I am able to open the accompanying data file without issue so the problem is limited to the calendar. I am wondering if there is an issue within the "upon opening" or "load settings" scripts?
Thanks

Hey Shawn,

This is the only known issue if you're running XP. Could this be it:

viewtopic.php?f=25&t=3121&p=7300&hilit=crash#p7300

Let me know.

Hi Jason,

Thanks for you rapid response. I have begun to take the steps outlined in the post, but I cannot seem to access the screen shot regarding step 2.

Thanks again!

Ok, I think I fixed it.

Sorry about that!

OK, now I am on step 7 and it reads:

In SeedCodeData.fp7 select File / Manage / External Data Sources and remove the reference to SeedCode Complete. Close the files and re-open them.

When I navigate there I see one item listed as:
Interface File Filemaker File Path: file:SeedCodeComplete

Do I just delete this?

Thanks

Right, we don't want SeedCodeData referencing anything. Delete away!

Thanks for all your help. Hopefully this did the trick!

Yes, please let us know.

Thanks!

Hi Jason,

Everything opened fine this morning, but I did notice one difference since making the changes. On the contacts layout, where the events are listed in the events portal, there used to be a strip of color on the extreme left of the event that corresponded to the event status. It isn't critical to restore this, but I was wondering if there was a quick fix?

Thanks again.

Good Morning,

That strip is the field z_sc_ColorCalc in events. This should have been corrected when you redirected it to look at CalendarColors rather than CalendarRows from the UI file. I'd double check this part.


5. Change the definition of the field z_sc_ColorCalc in the Events table of SeedCodeData.fp7 to be:

Code: Select all

Let ( [

    s = Status
   
    // Above is the field you're using to color code events. This doens't have to be an event status

//-------------- You shouldn't have to edit below this line ---------------

] ;


    If (
       not IsEmpty ( s ) and not IsEmpty ( CalendarColors::Name )
    ;
        TextColor ( CalendarColors::z_CalendarColorGlob ; CalendarColors::ColorRBGValue )
    )

)

Let me know if that helps,
Jason

Hmmm, that is exactly what I have for the field definition.

Should this field be selected as CalendarEvents:: z_sc_ColorCalc or ContactEvent:: z_sc_ColorCalc ?
The latter results in a blank space, the former outputs "<unrelated".

Hi,

You want it to be the same context as the portal, so Contact Events.

Not sure why it's not working. I can take a quick look at your files if you'd like. You can send them to [email protected], please include the full access account and password. If they zip bigger than 15MB you can use a service like SendSpace.Com.

-Jason

I think I found that my problem lies in my changes to the apply color settings {close, dont refesh} script.
I am having difficulty entering these steps as presented:
Set Field [CalendarColors::z_CalendarColorGlob; CalendarRows::CalendarColorGlob]
and
Set Field [CalendarColors::z_FieldForColorGlob; "Status"]

Hi Shawn,

Once you've added the fields to CalendarColors in step 1, then you should be able to update the script. Here's a quick screen cast of this

http://screencast.com/t/AJvpj67QR3Sk

Let me know if that helps,
Jason

Perfect! Additionally, I have closed and opened in the database multiple times today so it looks like my problem is completely solved.

Thank you for all of your help!