eremaut

Hi, You can't use XSL with the web companion (vs CSS you can). The XSL transformation will only work (for the moment) when exporting / importing to XML data. Sorry, I was also a requestor for this option ... better luck with FM 6.5

Hi, Yes, I believe indeed this was your first question. We have drifted away ... --- The best you can do now is something I already spoke about. Built in (as many as possible) personal banners from this first agent ... on splash screens, on printed reports, things like address and name of the agent, etc ... By this you don't prevent it from giving away to a second agent, but when they start using it, the will be confronted with the info of the agent colleague. A fearly good psychological block ... An other solution. When they use your appl. they should start by given a password and a click on a OK-button, no? Or any other important starter button will also do ... Well, built a 'Send Mail' step in on the script of this button, to send a "Start application" message to a dedicated account in your company. By this you will know when and who's using your application, yeaah ... If it's by an unauthorised agent, send them a bill, and I don't mean Clinton here :-) OK, they can close down there mail client application to prevent any further messages. But, you will receive in 99% of the time a first message, nobody is expecting this to happen! And then you have a proof in hand ... BTW, can also be used to knock on agent 1, because his's in fact the giveaway boy ... PS: Yes, true, this will also sent mails every time agent 1 start's (legitimatly) your application. No harm, this info (date/time) can be used for statistics ... therefore use a dedicated account and not your personal email account ! Regards,

Hi Dj, I can't go back channel since your email address seems to be incorrect? regards,

Hi Bob, You wrote: If you are not using a portal you have to create a new record in the related file with an external sub-script. In that case, you should have a global field in the parent file that you set equal to the parent key value (using a set field command), and then in the child file, create new record and set the child key field equal to the global field in the parent file (using a set field command via a constant relationship*). ---- No don't need to have a constant relationship to do this. You can set a global field in the child file (equal to the parent key value) even before the child record is created. For this to work you can use the existing parent/child relation! This will work when you run a script with the Set Error Capture Error [ON] and will work only for global fields. Then in the child file, create a new record and set the child key field equal to it's own global field. Your ready ... This little trick will even work if the child file is completely empty, so no previous records in the child file. You only must use Set Error Capture Error [ON] to get this thing working. Even more to say. This writing to globals will even work on locked records, in child or parent files, doesn't even matter. As long as you are using Set Error Capture Error [ON] lines in your scripts ... Now a hear other readers saying wooooowww is this true? Yes it is ... So, there should be no limit on data moving accross your FM solutions. Regards,

Hi Dj, Without going into every detail here, it just would take to long. But I would like to add some comments here: * First it's clear that every protection can and will be broken someday. * We don't use so called "fully functional demos", no need to do that. If you want to give the user an idea of how your application will look and feel, then an application with limited records possibility or with reports with many DEMO banners on it will do a great job. Our demo comes with only 90% of the normal functions of the real application. Secondly, our demo application (FM Developer based) is coming on a copy protected CD. This CD needs to be inserted before the FM application will launch. Up to today this CD can't be copied even with the latest CLONE CD 4.x softw. Okay, one day will come that we see a crack for it ... but by then I will have changed for a new CD copy scheme. * >Do you mean by clever scripting dedication of 90% of your time for protection against piracy an 10% for implementation of your solution? No, I mean with clever scripting you can go a long way by doing things yourself before the need of buying a plug-in solution. These plug-in's will give you extra possibilities but will also increase the price of the application. For many of our users this counts ... * >Hey man, that is the only working protection that you have. Instead forget those you've created. No, we will not. It's thrue that we use a base of this FM system. Buth the FM system is far from complete to handle all the needs for user settings needed in a real life application. How - for example- will you give the administrator of your application (running at the users site) a tool to create new users for there application? How - for example - will you prevent users from running the application on a friday, saterday and sundays while they are allowed to run it on the other days of the week? For all this you need to develope a user-menu system where usernames, passwords and access settings can be stored and set by an administrator (without knowing your own FM master/developer password) ! * >The following is not true. The startup script allways executes >If you think you migth contest some of above, I'll be glad to prove you it's validity. Well, I'll take you up on that one ... only this one, it would just take to long. >The startup script allways executes ... This is true and not true. You are right, it's possible to open a file via a relationship and the startup script won't execute. But this you can prevend from happening by not placing related fields on the opening layout. The FM access privilges (base system) must be set to prevend the creation of relationships with files from others ... In our application all files are checking the other files when they startup. When not loaded in the correct order, the application is quiting. The loading of the files are handled by a front loader (FM file). The only purpose of this loader is to startup the other files with the correct FM access priviliges (base system as we spook before) and in the correct order. This loader can only be loaded by the master menu-system ... and to make it even more confusing, they are in fact loaded not by the startup script but by the closing script ! Believe me, I've done some testing here. I spend five weeks of development of this loader system only ... needless to say that many items (username, passwords) in this system are encrypted. Regards,

You wrote: What I would like to see in FM is DEVELOPER LEVEL ACCESS, ie when you open your files with developer password the statrup script won't execute. In any other case no matter how the files are opened (via relartionship, by selecting perform script step from another file, creating value list from another file) the startup script should execute. --- Well all these things are available in FM, it's just a matter of clever scripting. Things starts by writing a good user-menu where all user actions can be monitored. It's there you can store the priviliges of users (forget the privilegs that comes with the FM client) and it's there you can also see wether they are already online or not. No plug-in needed for this solution ... Regards,

Hi, Yes, 2GB, but from that moment compression starts and the capacity can go well beyond the 2GB. How far? Depends on the kind of data and poss. to compress ... Needless to say that performance will decline! Regards,

Hi, We use it, is working real fine. What seems to be the problem? regards,

Okidoki! Pardon us ... I rest my case regards,

Hi, Still not 100% clear to me, but i guess you are trying to print the related records (the open invoice) from the customers (master records). It's like printing the detaillines of orders (db detaillines will be the childs to the orders db). Well if this is the case then yes when printing from the master you will see only one related record (the first) in your body ... To solve this problem you have to print from the related (child) records, not from the master records. So your print layout must be there, put the info of invoices in the body there and it will work ... You do like this: * Find in the customer db the open invoices * Via script you transfer control to the invoice (open ext. script ...) * In this script you go to the correct layout and handle what's needed to print correct * Return back to the org. script in the customer db, inform the user about finished print task That's it

Ok, sounds fine with me. By now Aubrey should have very a good idea how and what to start scripting ... BTW, will you be at Devcon 2002 ?

Hi, I'm sorry Tom but it will work. At least, I hope Aubrey has a 'new' record button in his application (somewhere) ... * Find button to get into find mode * Click checkbox Cats (can even be combined with color) * New button (gives a new find empty window, to perform the AND over CB's) * Click checkbox Dogs (can even be combined with color) * Enter Tell me, what's wrong here ???

Hi, Forget the plug-ins, they cost you money. You can do all this with a good scheduler software (many free available). Create a Filemaker file with auto starting script to perform whatever you need. From the scheduler you can launch this file at des. time ...

Hi, Don

Hi, Just testing ...