The Separation Model

Hi! I have a solution with a db file with all the tables, a business logic file and several UI files. I opened one of the larger UI files and turned on IWP. Seemed to work fine. Closed it and then decided to rename it. And now I'm locked out of it! Just using one username and password (admin with full access). I managed to provoce this behaviour with other files as well. Couple of days work went down the drain, guess I must blame myself for not having a backup. Is this something anyone have experienced before (and I don't mean sloppy BU routines)? Regards!

I'm about to use the separation method in migrating an FMP6 project to FMP7. Is keeping the _DATA and _BR tables in sync going to be a problem? In the many-to-many example, the _DATA and _BR database table records are added/deleted explicitly in the scripts in the interface database. In production implementations of this model, is this the method used? That the records are added/deleted separately and the operation limited to being performed in one place. Would using the relationship, "allow creation..."/"Delete related..." settings be more effective? Set on the _BR table relationship for the primary link to the _DATA table. Again, though, this requires that a…

I am in the early planning stages of a database for my job (the application should be installed by the time we go back after Winter Break). I used (but really didn't design with - tweaking and dabbling only) previous versions at a couple of previous jobs three and more years ago but I can see that FM 7 is quite different. The DB I am planning will have 50+ fields total. Right now I am trying to get my mind around how many tables (and occurrances of tables - sheesh!) I am going to want to create and whether or not I want to actually have separate files or just separate tables. I will be the only user for the foreseeable future. I have been going through the VTC CD an…

SCENARIO: I have 8 related tables in a single FM7 file, primarily using a star join. The GUI layer used for printing is a separate table which contains the many required layouts, most of which use PDFs with related fields overlaid where required, or text with merged fields. This is done to seperate data from the presentation layer, so that a change in one or more of the PDFs can easily be updated without disrupting the data. INTENDED BEHAVIOUR: The "template" table contains many layouts but only a single record - the record to be printed. The relationship with the "template" table is via a global field; it contains the primary key of the record to be printed from the…

I have justed started work on a new system, I have spilt the files so far into data and interface (business logic to come later) however as I am starting to work on the layouts I realised I had not created all the fields needed. When I add additional fields to tables in the data file I cannot then see them in the interface file to put on the layout. If anyone has experienced the same problem or better yet knows what I am doing wrong, your words of wisdom would be much appreciate. I am using FM Developer 7.0 v3 on a Powerbook G4 1ghz 10.3.6 laptop. Thanks G

Hi folks...FM 6...developing a contract / client /production database solution for a local publisher and have been able to implement the SM to a farily large degree and with good success. The business publishes multiple publications. The db is in use but there is one area I'm having difficulting with is searching contract data. Three essential elements at play: Clients (1 Client) Contracts (Can have multiple contracts linked to Clients via ClientID key) Ads/Production Info (And hundreds of ads linked to Contracts by unique Contract Numbers ) Data files: Clients (ClientMan), Contract (ConMan), Ad/Production Ordering (ProMan) one user interface file cal…

I

so I have a database of about 27 contacts people. I want to make a login and password for each these and have the user only able to see or edit there own information and then use instant web posting. from what I read i have use scripts is this the right path. thanks for any help.

I'm migrating my solutions to FMPro7 and I decided to use try out the separation model for my main data files. At this point I'm hoping the extra effort will actually pay off but I'm already seeing that this complicates matters. For example, the types of modifications I most often make to our solution most often involves the creation of a new field definitions as well as modification of a layout. FMPro7 doesn't really save data in a separate file - the Field Definitions must be stored in the data file. This means I can't make changes without taking the solution offline. Also I now have more than one file to modify: My layout file and my data file. So what's the poin…

Hi, Has anyone succeeded in building a really complex solution based on 3-file separation model scheme? If so - could you please share your opinion on this.

I have just begun work on a new database in FM7 for my company. It will be used to manage our customer relations which involves a number of

I just spent a whole day developing an app with data tables in one file (database name <appname>d.fp7) and the layouts, scripts and relations in another (database name <appname>i.fp7) I got it working great, until I tried to use web sharing - no data showed up at all and I had conniptions. I think I have <appname>d.fp7 web sharing on, as well as web sharing for <appname>1.fp7, but data doesn't show on web browser. Bad news. Large widely used apps are exactly the ones you need to do separation on AND get on the web. Someone tell me I'm stupid please, and that there is a way to do it!! By the way, while I'm waiting to see if t…

I've been working on an implementation of the separation model and have found a significant problem. Things were progressing fine until I implemented an audit trail -- using Nightwing AuditTrailTest.zip

I am wondering how to employ the new security system (management of accounts and passwords) in the separation model. I assume that all security settings should be the same in both files (data and user interface) ? If so called 'super users' are allowed to create accounts, how do you manage this in a secure way ?

Hello all, i had to edit this Post. After several reads i came to realize i misunderstood the concept of seperation. now the question is; what benifits exactly does seperation of gui and data bring? easy modifieng of gui without interrupting the db? Or also some stability and robustness? anybody know? regards, Overrider

Hello, I'm currently rebuilding my FM 5.5 application to get familiarized with FM 7. The separation model appeals to me so I'm trying to keep the tables in one (data) file and all layouts, relations, scripts etc in another (layout) file. However, I have some calculated fields based on other tables and I can't figure out how to get them to work without adding relations to the data file. For example, I have a parent table, INVOICE, with two child tables, LINEITEM and PAYMENTS. In my old solution I had a calculated field, OUTSTANDING, in INVOICE that subtracted LINEITEM amounts from PAYMENTS amounts. The field OUTSTANDING was later used for a value list so that whe…

Ok, I've decided to try the separation model for the new multi-location inventory system I'm putting together, basically my data will be separated into 3 main tables, Location Master, Item Master, and Item/Location (which will house the actual quantities). These are the fields I have in each table Item Master: Item#, Description Location Master: Loc Code, Description Item/Location: LocCode, ItemCode, Quantity, UID (an auto-enter field which is the LocCode & ItemCode, there is a not equal self-join based on this field to ensure uniqueness based on both location code and item code at the same time). Now, using the separation model I should have the layouts …

Hi, When FM7 came out, I decided to be a good boy this time and read the manuals. They are advocating the Separation Model (SM) wherein the solution is split into three files: one for layouts and scripts, one for calculations, and one for the data. This is great (in theory) as it will make repurposing the solution or updating the solution for off-site users very easy. In the attached file I've simulated this in one file by making a data table (People), a calculation table (Calculations), and a layout table (Calendar). Each record in the data table has a related record in the calculation table where the calcs take place. In the calendar table the user ent…

I think, like most of us, I finally have my brain (partway) around the new structure. I am now experimenting with how to convert my existing solution to FMP7. But I am alittle scared to make a naive mistake(s) that I will regret later. When is it appropriate to create a solution that is made up of multiple files, each containing multiple tables? Take a common structure we all are familiar with. A database containing a table of people, invoices, lineitems, and items. In this hypothetical example there are also a couple of lookup tables for info that isn't transactional. Is there a situation you would want this in multiple files? I hope someone can shed …