Database Check

[Matthew R White]

Hi all,

I'm very new to filemaker.

What I'm really struggling with, is that I'd like to set up a server for my database, but I need the data, after its been entered on a client computer, to go through another specified client computer and be checked (by one of my employees for accuracy) before being applied to the database.

Is there an easy way to do this?

1 million thanks!

Matt

[comment]

Yes and no. Yes, it's possible - but not in the way you describe. The data entry person must enter the data into a "database". This could be a temp table in your solution file (or another file). Then your employee could verify the data and import it into the "real" table. Alternatively they could enter it into directly into the "real" table, but it would be considered suspect until your employee marks it as approved.

[Matthew R White]

Ok, sounds great, how do I implement this?

[Matthew R White]

BTW I really really really appreciate your response. This is a huge issue at my office and I'm tasked with figuring it out.

[comment]

how do I implement this?

I am not sure how to answer that.

[Matthew R White]

What I mean is, what's my next step. Do I need to find a certain script to get filemaker server to do this, is there a setting I need to enable, how do I make this happen?

Thanks again

Matt

[comment]

Forgive me for asking, but have you ever done anything in Filemaker? The tutorial, at least?

[Matthew R White]

Yes I've created and designed layouts, wrote basic basic scripts such as printing certain pages. Thats the extent of my filemaker knowledge.

[comment]

Well, then you should know how to add a table to your file, say we called it Temp. In addition to the fields you need for your data, let the table also have a ApprovedDate field (type Date) and ApprovedBy field (type Text). Write a script named Approve that sets these fields to the current date and account name, respectively. Write another script that [a] finds records in the Temp table where the ApprovedDate field is not empty; goes to a layout of your "real" table; and [c] imports records from the Temp table into your "real" table.

There's probably a lot more work to be done here. For example, you'll want to prevent importing the same records over and over. Perhaps you need to set up separate privilege sets for the data entry person and for the checker. Hard to say, as you haven't really provided any details.

BTW, this has nothing to do with Filemaker Server. You need to develop your solution in the Filemaker Pro (client) application. When that's done, you can use the server application to deploy it.

Edited August 12, 2011 by comment

[Matthew R White]

Excellent response, now I have something to work towards. Are you aware of any examples of this, such as written scripts or sample databases that do this that I can model after?

Thanks again,

Matt

[comment]

The closest thing I recall is someone asking about entering data twice (by two different people).

[bcooney]

It is amazing that your management has decided that it's very important to "approve" all data entry, but it's not important to have a developer that knows what they're doing mess with their production system.

Since we haven't been provided the details as to how "separate" the unapproved data entry needs to be from the approved data, then I can't comment on which of the two approaches *comment suggested would be more suitable to your requirements. I will tell you that adding a simple field "Approved Date" is a much easier functionality to achieve, and perhaps that would the approach you should first consider. Then, you can use Find to list the "approved" vs the "unapproved" records.

[comment]

I agree - on both points.