Yvonne Garcia

I'm having a similar issue, limited to one client out of about 12 running the solution. Have not come up with a solution yet but will post if I do. Please keep us posted, Henry, if you find a fix. Thanks, Yvonne

Thanks for the redirect to this thread, Martin. Rindin, here is what I did to have guest access and also account-level access (based on Martin's suggestions): Data.fp7 = guest account enabled, as well as each individual account. Restricting guest to certain layouts, fields, etc. Input.fp7 = guest account disabled. Contains each of the other individual accounts. This contains a file reference to Data.fp7 so I'm able to get some initial functionality without duping data (such as limiting the initial record viewed to the one belonging to that user). After the initial stylesheet, the rest of them go back to referring data.fp7 so I don't have to recreate the rest of the layouts in this file. This is testing well, with the password request coming up once someone gets to this stage. Only thing I still need to figure out is a "log-out" because my client would feel more secure with one. I think I'll play around with invalidating the session. I'm new to session work. Any ideas? Thanks again, Yvonne

I have a FMPro 7 solution running on FMSA to the web via CWP and XSLT I have three privilege groups: guest: read only access admin: full access contributer: edit/create access (can't delete) If I turn off guest access, everything works fine as far as who has access to which records and commands. Once I enable guest, it defaults to that whenever a user goes to the site (which is exactly what the documenation says it will do). The documentation says to use the re-login script to allow a user to login as someone other than guest. I've played with "Re-login" and could only get it to work by creating a stylesheet with a user field and a password field on it in order for the script to work. The problem with that is that it bypasses the browser authentication and breaks everything that uses the "client-user-name" parameter. Users also need to be able to log-off. I can't get the "Exit application" script to trigger correctly for this to happen. Is there some way to allow for a user to log-on as something other than guest using browser authentication? Is there also a way to log-off as one user and then log-on as another? TIA, Yvonne

My first thought was that the id_master field was missing from the portal as well. But, alas, it wasn't. I rebuilt the layout and that did the trick! Thank you very much, Martin.

My first thought was that the id_master field was missing from the portal as well. But, alas, it wasn't. I rebuilt the layout and that did the trick! Thank you very much, Martin.

My first thought was that the id_master field was missing from the portal as well. But, alas, it wasn't. I rebuilt the layout and that did the trick! Thank you very much, Martin.

Martin, Thank you for the great explanation and the code. That worked well with the Personnel situation I outlined. After reading your post, I thought I understood the issue with "Context" so I tried my hand at another similar situation. However, I wound up with the same problem I had with the Personnel situation. It looks like a link but the variable isn't being passed. Can you point out where my thinking/coding is flawed? Here's the code I created based on the personnel example you shared with me: <td align="left" valign="top"><br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <!-- variable definition here --> <xsl:variable name="whynot" select="fmrs:field[@name='Project_Open::id_master']/fmrs:data[1]"/> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/></xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <!-- use the variable here --> <xsl:with-param name="id_master" select="$whynot"/> </xsl:call-template> </xsl:attribute> <xsl:value-of select="."/> </a> </xsl:for-each> </xsl:for-each> </td> It DOES work if I go back to my clunky workaround of linking on some static text instead of the dynamic field: <tr> <td> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <xsl:value-of select="fmxslt:break_encode(.)" disable-output-escaping="yes" /><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> <td align="left"> <br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::id_master']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <xsl:with-param name="id_master" select="."/> </xsl:call-template> </xsl:attribute> (view) </a><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> </tr> Thanks in advance for the help and the education. - Yvonne

Martin, Thank you for the great explanation and the code. That worked well with the Personnel situation I outlined. After reading your post, I thought I understood the issue with "Context" so I tried my hand at another similar situation. However, I wound up with the same problem I had with the Personnel situation. It looks like a link but the variable isn't being passed. Can you point out where my thinking/coding is flawed? Here's the code I created based on the personnel example you shared with me: <td align="left" valign="top"><br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <!-- variable definition here --> <xsl:variable name="whynot" select="fmrs:field[@name='Project_Open::id_master']/fmrs:data[1]"/> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/></xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <!-- use the variable here --> <xsl:with-param name="id_master" select="$whynot"/> </xsl:call-template> </xsl:attribute> <xsl:value-of select="."/> </a> </xsl:for-each> </xsl:for-each> </td> It DOES work if I go back to my clunky workaround of linking on some static text instead of the dynamic field: <tr> <td> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <xsl:value-of select="fmxslt:break_encode(.)" disable-output-escaping="yes" /><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> <td align="left"> <br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::id_master']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <xsl:with-param name="id_master" select="."/> </xsl:call-template> </xsl:attribute> (view) </a><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> </tr> Thanks in advance for the help and the education. - Yvonne

Martin, Thank you for the great explanation and the code. That worked well with the Personnel situation I outlined. After reading your post, I thought I understood the issue with "Context" so I tried my hand at another similar situation. However, I wound up with the same problem I had with the Personnel situation. It looks like a link but the variable isn't being passed. Can you point out where my thinking/coding is flawed? Here's the code I created based on the personnel example you shared with me: <td align="left" valign="top"><br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <!-- variable definition here --> <xsl:variable name="whynot" select="fmrs:field[@name='Project_Open::id_master']/fmrs:data[1]"/> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/></xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <!-- use the variable here --> <xsl:with-param name="id_master" select="$whynot"/> </xsl:call-template> </xsl:attribute> <xsl:value-of select="."/> </a> </xsl:for-each> </xsl:for-each> </td> It DOES work if I go back to my clunky workaround of linking on some static text instead of the dynamic field: <tr> <td> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::prj_title']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <xsl:value-of select="fmxslt:break_encode(.)" disable-output-escaping="yes" /><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> <td align="left"> <br/> <xsl:for-each select="fmrs:relatedset[@table='Project_Open']/fmrs:record"> <xsl:for-each select="fmrs:field[@name='Project_Open::id_master']/fmrs:data"> <xsl:if test="position() != 1"><br/> </xsl:if> <a> <xsl:attribute name="href"> <xsl:call-template name="link-prjrecord-pi"> <xsl:with-param name="id_master" select="."/> </xsl:call-template> </xsl:attribute> (view) </a><br/> <xsl:if test=". = ''"> <xsl:text disable-output-escaping="yes">&nbsp;</xsl:text> </xsl:if> </xsl:for-each> </xsl:for-each> <br/> </td> </tr> Thanks in advance for the help and the education. - Yvonne

I've searched through the archive and can't quite find an answer to this issue. Any help would be appreciated. Here's the background info: FMPro 7 Advanced shared via CWP. One file, multiple tables. One table is Projects; another table is Personnel. I can get the Personnel related to Project to display, no problem using the following code: <xsl:when test="count(fmrs:relatedset[@table='Personnel']/fmrs:record)>0">

Thanks for the replies, Stanley and Ralph. I didn't follow my normal operating procedures with this project because I was in a bit of a hurry to get to the client site. Fortunately, I have found a copy I can get into. Lesson learned the hard way but it could have been much worse. And now my fallback procedure is now back up and running in full measure! - Yvonne

I am trying to open a database I developed and none of the users/passwords I have for it are working. I've gone through the list of possible passwords systematically (lower case and upper case) and cannot get back into the file. I am sure it is something I (or my client) did. I have called FileMaker and they do not offer a password recovery service for FMPro 7; neither does lostpassword.com. I'm thrilled that FMPro 7 is so secure but dread the idea of recreating 60 hours worth of development work. Does anyone have any ideas/tricks/tools about how to break into a FMPro 7 file? It is truly a legit need. In desperation, Yvonne

Thanks, Jean-Marie, that was exactly what I needed! - Yvonne

Currently I have a stylesheet that will take exported FMPro data and convert it into an html file with a simple table: one row per record with three columns to match the date. For example: ___________________________________________________ |image source info 1 | image name 1 | description 1| ___________________________________________________ |image source info 2 | image name 2 | description 2| ___________________________________________________ What I would like is for each record to span two rows, like this: ___________________________________________________ |image source -> | image name 1----------> | |info 1 here ---> |_____________________________| |[space here] --> | image description 1------> | ___________________________________________________ I don't know enough to make this happen and am wondering if someone can point me in the right direction? Thanks in advance, Yvonne

Wow, Doug, that was great work. Thank you for it. Opening the FileMaker II file with FMPro 2 worked fine. Then from there, the file was easily converted to FMPro 6. Thanks Doug and Stanley for sticking with this.

Amazingly enough, Apple still has a trial copy of FMPro 2 on their FTP site. I've downloaded that and will see if it will work with the FileMaker II file. Stanley, I know that FMPro 3 can deal with FMPro 2 files; this is an older FileMaker II (before the Pro versions came out) so it isn't quite the same. I have high hopes that FMPro 2 will work, though. I will post the results as soon as I have tested this. Thanks for the feedback and suggestions. - Yvonne

I'm trying to find documentation for the upgrade path for a FileMaker 2 (not PRO) solution. Does anyone know what the most recent version of FMPro is that would convert those files? TIA, Yvonne FileMaker Version: Dev 7 Platform: Mac OS X Jaguar

I have several 24/7 FMPro/web solutions running off of the older iMacs without any problems. Here's what we use to reduce down-time: * Kick-off to reboot automatically if the system crashes * Appropriate alias to files (like a db opener on the FMU machines and the FMS on the FMS machine) in the start up items folder * Timbuktu for remote administration * Backups are handled by FMS and backup to both a local FW drive and across the network using Dave (we're not on OS X yet). While you could host the database for the web and for the lan using just FMU, FMS allows for quick/painless automated back-ups without taking the databases offline. Otherwise, backing up the dbs requires some ugly workarounds. If you do decide to use both FMS and FMU, follow Vaughan's advice and put them on separate computers. Good luck, Yvonne

Sorry for the late reply. Thanks, Jeff. That worked perfectly. Now I can get my RAIC back online. - Yvonne

Anatoli, I've followed the procedures outlines in FileMaker's "Web Publishing Security Guidelines", from where not to store the databases to limiting which databases get shared via the web to using the security databases for password protected access to more sensitive information. Your question has me worried that I've missed something, however? - Yvonne

Steve, thanks for the reply. You can run WSC on OS9, no problem. We are running it using the OS9 version of WebStar. It's been working great until this pesky proxy port problem was discovered. I can't restrict db access to specific IP addresses since it is a public website. For now, I've had to disable the Webstar server and go back to serving up the website using just one iMac. Still looking for a solution... Will post it if I find one. - Yvonne

Hello Everyone, I have a client configuration running Webstar with Web Server Connect one one iMac, FMPro Server on one iMac, and FMPro 5.5 Unlimited on two other iMacs. All iMacs are running OS 9.x. Recently, I was informed that the Webstar server constitutes a security breach for my client because it has an open proxy on port 8000. I reconfigured Webstar (and restarted it) to limit to and from access on the proxy to only the IPs used by the four iMacs. However, the proxy is still coming up as open to the public on the security tests and so we are having to shut down Webstar and go back to using a single iMac as our web server. I can't find any other way to limit the proxy and don't understand why setting allow privileges did not work. Any input as to what to try next would be greatly appreciated. Thanks, Yvonne