Jump to content

Soenso

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Soenso

  • Rank
    novice
  • Birthday 11/28/1977
  1. When attempting to connect using SFTP using FTPeek_ConnectSFTP function, FTPeek_LastError returns "Failed to read messages". I attempted to resolve the problem by downloading and installing the latest version of the plug-in today. That did not resolve the issue. I've attempted to run the script from Filemaker 12 Advanced and Filemaker 12 Server.
  2. Just curious if you've had any success parsing the Eve-Central.com API. Took a stab at it this morning and I think I figured it out.
  3. The installation files I have only contain the .dmg files. I have the email with the hyperlink to the app and documentation download, but as you know, those download links expire after ninety day. Oh well. I'll call Filemaker and see about getting another copy. On a side note, my 900 kb filemaker file exploaded to a 100 MB runtime package! Sheesh, is that normal? Perhaps it's not as odd with larger solutions, as there are certain fiales that have to be there no matter what the original filemaker file size was.
  4. Thanks to both of you! I thought maybe I'd have to have FM Advanced installed on Windows to create Windows runtimes. And there's the rub. I stupidly neglected to download both the mac and windows installers for FMP Advanced when I bought it. I have the key, just no installer. Guess I'll have to tackle that problem first...
  5. I'm trying create my first runtime solution from Filemaker Pro 10 Advanced (Mac OS X). The database from which I'm creating it is small (for now), about 900 kb, and utilizes only two layouts and a handful of relationships. I thought I'd start simple. It may be just my ignorance, but Filemaker's documentation on runtime solutions is terrible and inadequate, at least for me. I'd prefer to create a solution that is cross-platform, but for now I'd just be happy with one solution I could install and run on Windows, and one I could use on Mac OS. I've used the Developer Utilities feature to bind the files, and have used what (I think) is a unique 3 letter extension. What do I do with the created files? So, how do I a.) create a runtime solution that can be installed on Windows, and b.) do I need a separate installer? I'm having a hard time finding any solid information on just what to do. Thanks in advance
  6. Happy Thanksgiving. Yesterday I wrote an import script to do just that. The whole import took about an hour. 100% of the records and fields imported without error. The only unconventionality about the server is that the previous IT administrator split the entire 500GB drive space into two partitions. Unfortunately, the OS partition is only 10GB. Though annoying, this really wasn't a problem with previous versions of FIlemaker Server that didn't have to be installed on the same partition as the OS. But now, between Windows Server 2003 OS and FMS9, I don't have much space to spare (less than 500MB), so my hosted files are stored on the other partition. I try not to make it a habit to make schema changes during database use, though I'll admit, there's been a time or two that I had to. Also, I've recently prohibited connection to the database via wireless connections. All of my client machines have battery backups and surge protection. Hopefully my import will make the difference and address the corruption. The file has been up for a day or so, and my intraday backups have been completing without error.
  7. I opened the database and saved a compacted copy from the File menu (then used the compacted file). I did not use the maintenance utilities. I do have backups from before this all started, with relatively few database schema changes. There has been quite a bit of data changes since those backups, though.
  8. Hi all, (forgive my long story, but I figured the best policy was to give as much info as possible) I just recently (this month) upgraded to Filemaker Server 9. My FMS9 installation is up to date, and all of my client installations are running 9.0v3. (FMS9 is running on Windows Server 2003 OS). A database which has been in use since June 2007 has started acting up since the upgrade to 9. About a week ago, the database closed, kicking out all users. Server could not reopen the database. I opened the file locally and "Saved As Compacted". (Should have instead reverted to a backed up copy, I'm sure) Once that was complete, I replaced the existing file with the compacted file. Server was able to open the file and users were able to log back in. Everything behaved normally for about a day, until a user discovered a portal record with no data. I found the ghost record in the table (each field replaced with the value, "?"). I decided to go into that table's settings and remove indexing on all the fields, then committed the changes. The ghost record disappeared. I then went back into the table and set indexing to "All" for each of the fields I had previously changed. Everything behaved normally for a day or so, but at some point later, Server was unable to verify the integrity of the backup. Fantastic. Weary of possible corruption, I saved the database as a clone and opened the clone in server, running a backup on the clone. The clone's integrity was verified by Server. Considering my schema to be clean, I compacted the full database (not the clone) and then opened the file in Server and ran a backup. The backup was verified. Great. That was Friday. My backups over the weekend went without issue. Today, users were reporting that Filemaker was hanging up (all users are running Windows XP). They were getting the "coffee cup" and when they'd click in the interface, the OS would report that the database was "not responding." In some cases, the database would complete what it was doing and allow use again. I determined that the lag was occuring when users attempted to write to the same table that'd had the ghost record and that I'd reset the indexing settings for. Betting on a hunch that I might have had some block level corruption in that table, I backed up the file (without issue or error) and then exported all the records from that table, deleted all 60K records, and then re-imported them (and updating my auto-generated serials). I then compacted the file one last time. The resulting file was about 70K smaller than the original pre-export/delete/import file. I opened the file, and everything looked great except for another ghost record that appeared. I once again reset the indexing, but this time, instead of re-selecting "All", I selected "update index as needed." The file is open, and I have noticed some reduced performance when writing to the problem table (that performance has improved slightly for me on my Macbook Pro, but I'm concerned my users might see the same issues again tomorrow). Any ideas on what might be the issue? I suppose that the performance issue on that table might, at this point, go away once the indexes have been rebuilt. It also could have been a difference between setting the index to "All" verses "index as needed". Every other part of the database works without issue. Could it be that I just haven't optimized Server 9 since installation? Any client installation configuration changes that I need to make? Thanks for your input.
  9. Yeah, I thought that might be the issue. Filemaker behaves the same regardless of whether Outlook Express 6 is launched or not.
  10. I checked my Internet Options and Outlook Express is my default app for Email.
  11. I attempted to send mail via the Filemaker "File>Send Mail.." menu item. I get the send mail dialog window. I entered my email adddres, a subject, and some email body text, and sent the mail. I checked Outlook Express, and found that there are no emails in my "Sent Items" or "Outbox" folders (I know that Outlook Express is configured properly, because I can manually send mail from it). I configured Outlook Express' security settings to warn me when an app tries to send mail through my account. I am not getting that warning.
  12. bcooney, I attempted to send mail via the "select Send To>Mail Recipient" method you mentioned. It did nothing (just like the "send mail" script). A quick Google search took me to the following website: http://windowsxp.mvps.org/sendtomail.htm It stated the following problems: - The default mail client is not set - The MAPI DLL registry path for your mail client is missing It recommended running the following commands: regsvr32 sendmail.dll "%ProgramFiles%Outlook ExpressMSIMN.EXE" /REG regsvr32 "%ProgramFiles%Outlook Expressmsoe.dll" After having run those commands, I am now able to send mail via the "Send To>Mail Recipient" method. The Filemaker script, however, still does nothing. Thanks for your help.
  13. When you say that you "have a scripted lookup to filter to all the correct task records", do you mean that you are filtering portal contents, or filtering a found set of records? If you're filtering the found set of tasks, I think the following will work: The Go To Related Record script step has a result option that matches all the records in the current found set. If you are on a tasks-based layout and you want to view all the timesheet table records that relate to that found set of tasks, under the GTRR options, specify: Get Related Records From: Timesheets Show Records Using Layout: [Timesheets layout] [X] Show only related records ( ) Match current record only (o) Match all records in found set I could completely misunderstand your need or be way off. Hope this helps.
  14. I'm currently having the same problem on a Windows 2003 server. The send mail script step runs, but no email client is loaded. I can run the script on other computers within the office, just not the one system I need it to run on.
  15. I'm running Filemaker 8.5 on a Windows 2003 Server. I've installed MS Outlook 2003 and configured an email account using a Exchange account. I've also configured a POP gmail account using Outlook Express 6. I am unable to get either of these mail clients to launch when I run the "Send Mail" script. Any help would be much appreciated.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.