March 10, 200520 yr Author Premise: I am using FileMaker Pro 7 to create, manage, and publish a database of records that are ultimately intended for a website being hosted (purchased service) under FileMaker Server 7 Advanced. This website is ought to provide a secure user login, after which each user is supposed to view his/her records only. Problem: Since I am creating this database on FileMaker Pro 7, I have to intend it so far for Instant Web Publishing, which will be unnecessary, once it is hosted under FileMaker Server 7 Advanced. This means that I cannot yet alter any browser appearance (e.g.browser tags) other than through FileMaker's own layouts. This also means, that to test my DB online access through Instant Web Publishing so far, I am required to leave FileMaker Pro 7 open while accessing localhost:591 through my browser. Leaving FileMaker Pro 7 open has the unfortunate effect of setting the AccountName and UserName globals to the name of the user who is signed in through FileMaker Pro 7 directly. This means that though a different user logs onto the DB through the web, using IWP, this user will still only be recognized as whoever keeps the DB open through FileMaker Pro 7 directly. I hope that whoever understands my problem, or has/had a similar problem responds to my posting, because it has been a quite frustrating experience to get this to work, which might prompt me in the end to completely abandon the seemingly much more elegant and user friendly FileMaker for a mysql/php solution. Thanks in advance.
March 10, 200520 yr Premise: I am using FileMaker Pro 7 to create, manage, and publish a database of records that are ultimately intended for a website being hosted (purchased service) under FileMaker Server 7 Advanced. This website is ought to provide a secure user login, after which each user is supposed to view his/her records only. Problem: Since I am creating this database on FileMaker Pro 7, I have to intend it so far for Instant Web Publishing, which will be unnecessary, once it is hosted under FileMaker Server 7 Advanced. This means that I cannot yet alter any browser appearance (e.g.browser tags) other than through FileMaker's own layouts. This also means, that to test my DB online access through Instant Web Publishing so far, I am required to leave FileMaker Pro 7 open while accessing localhost:591 through my browser. Leaving FileMaker Pro 7 open has the unfortunate effect of setting the AccountName and UserName globals to the name of the user who is signed in through FileMaker Pro 7 directly. This means that though a different user logs onto the DB through the web, using IWP, this user will still only be recognized as whoever keeps the DB open through FileMaker Pro 7 directly. I hope that whoever understands my problem, or has/had a similar problem responds to my posting, because it has been a quite frustrating experience to get this to work, which might prompt me in the end to completely abandon the seemingly much more elegant and user friendly FileMaker for a mysql/php solution. Thanks in advance.
March 10, 200520 yr Author Premise: I am using FileMaker Pro 7 to create, manage, and publish a database of records that are ultimately intended for a website being hosted (purchased service) under FileMaker Server 7 Advanced. This website is ought to provide a secure user login, after which each user is supposed to view his/her records only. Problem: Since I am creating this database on FileMaker Pro 7, I have to intend it so far for Instant Web Publishing, which will be unnecessary, once it is hosted under FileMaker Server 7 Advanced. This means that I cannot yet alter any browser appearance (e.g.browser tags) other than through FileMaker's own layouts. This also means, that to test my DB online access through Instant Web Publishing so far, I am required to leave FileMaker Pro 7 open while accessing localhost:591 through my browser. Leaving FileMaker Pro 7 open has the unfortunate effect of setting the AccountName and UserName globals to the name of the user who is signed in through FileMaker Pro 7 directly. This means that though a different user logs onto the DB through the web, using IWP, this user will still only be recognized as whoever keeps the DB open through FileMaker Pro 7 directly. I hope that whoever understands my problem, or has/had a similar problem responds to my posting, because it has been a quite frustrating experience to get this to work, which might prompt me in the end to completely abandon the seemingly much more elegant and user friendly FileMaker for a mysql/php solution. Thanks in advance.
March 11, 200520 yr Author Problem solved -> Field storing Get ( AccountName ), which of course is the relevant one, was set to store data, among other "smaller" glitches.
March 11, 200520 yr Author Problem solved -> Field storing Get ( AccountName ), which of course is the relevant one, was set to store data, among other "smaller" glitches.
March 11, 200520 yr Author Problem solved -> Field storing Get ( AccountName ), which of course is the relevant one, was set to store data, among other "smaller" glitches.
Create an account or sign in to comment