Access vs. FileMaker

[sparlaman]

OK, I know this forum is for Q&A but I really need to vent here and this isn't exactly off topic. It is about Access...

Thanks to my employer's insistence on using FileMaker instead of Access my brain has been ripped out of my head, smashed, turned inside-out, and shoved back up my nose.

It has taken me a day and a half to figure out why I was getting the "you can't assign a value to this object" error on my form. The reason turned out to be because I was treating fields within one table as though they were in a one-many relationship. I was taking the employee data contained neatly in one table and splitting it up into categories via queries then trying to bring it back together on a form with sub-forms.

Why was I doing something so stupid??? Because in FileMaker everything is all mixed up then split up and then mashed together again in ways I just don't understand so my mind was not making sense of the simplest of relational database concepts.

Anyway... I wanted to put this up here just in-case anyone esle runs into that same error. To summarize if you have data contained within one table and you want to categorize the data on a form say via tabs. you don't have to do anything special with queries to split the data up or anything. You just create your form based on the query with all the pertinent fields and use the tabs to categorize. You'll be pulling fields from one place and you don't have to worry about master/child linking because the data is already in a one-one relationship.

yes feel free to give me the big Duh!

Thanks,
sparlaman

[NoellaG]

Hi Sparlaman,

I won't give you a big Duh, but perhaps a "lol" will do?

grNG