Jump to content

Teutonic_Night

Members
  • Posts

    53
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Northern Illinois

Teutonic_Night's Achievements

Enthusiast

Enthusiast (6/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I have a solution that helps keep track of file deliveries. We delivery relatively large numbers of files (so far, up to about 90k per month), and some of these deliveries are of the same file to multiple destinations. I need to create a list of all new deliveries in a given month, and all previous deliveries that have been invoiced. I already have a method to get a list of unique filenames, but I now need to search the "delivery" table for all instances of each unique filename delivered in a given month. For example, the table "deliveries" contains 1,000,000 records. In August we made 25000 deliveries, of which 15,000 were unique files. I need to search all 1,000,000 for every delivery for each of the 15,000 unique files that were delivered in August. Right now, I have a method that works but is awfully slow. It essentially performs 15,000 finds, with 14,999 expanding the initial found set. I was wondering if anyone had any suggestions for a method to perform a find such as this that would be a bit faster. I'm already using layouts with no fields on them and using the "set field" script command to set up my search criteria. I'm not searching on any calculated fields. This is on a hosted database, hosted by FileMaker Server Advanced 11, with FileMaker Pro 9 clients used to access it.
  2. I have a solution that needs to update records in a MySQL database based on actions in the local FM database. I have the ESS connection set up, can see all the fields I need, etc. The problem seems to be that I can only retrieve 255 records at a time from the MySQL database. I'm using the MySQL ODBC drivers from MySQL on a Windows 2003 Server running FileMaker Server 9 Advanced. FileMaker knows how many records are in the MySQL table (~25k), but seems to only be able to access 255 at a time. I haven't been able to find anything on FileMaker's site about such a limitation, so I'm wondering if it has something to do with the MySQL ODBC driver or perhaps the configuration of MySQL. Anyone have any suggestions or run into similar issues?
  3. Being new to using ESS sources, I didn't realize that FileMaker grabs the database and table name from the DSN and stores it locally without granting access to it to a developer. I was hoping that if the DSN was simply pointed to a new database, that FileMaker would just get the database and table names from the DSN as necessary, not just the first time the ESS is accessed. I don't think there was anything "willy nilly" about the database names- one instance was for development, and the second was for QA. I don't know why the MySQL DBA named them the way he did, but the tables and fields were all named the same, simply the database name was different between the two databases. Maybe it was because they were both hosted on the same server and couldn't have the same name. And I agree, some sort of search and replace capability would be a huge benefit.
  4. I also discovered that the tables in the referenced external database have to have their names remain consistent, not just the database name. The only thing that comes to mind as a work around is to insert some sort of go-between table, and have your solution's scripts and what-not reference that table instead of the ESS. I haven't fully thought this through, though, and I'm guessing that it could cause all kinds of latency or synchronization issues. And you'd still have to redo all the references to your ESS, but it *might* allow you to minimize how much scripting is impacted. Just an idea.
  5. I've run into a similar problem. We're looking at developing a FM solution to keep track of specific data that is related to data in a MySQL backend. The problem is that this is a fairly high-profile project, and we are being required to make use of different environments for the different stages of development. There's going to a be a dev, a QC, and finally a production environment. The problem I've encountered from some quick testing is that I can't seem to easily move which MySQL environment the FileMaker portion points to. I thought that all I'd have to do is change which system DSN the solution is using when setting up the different environments, but that seems to break everything. I'm not really looking forward to having to update every layout and script that has any ESS references included, so I'd love to know of a solution to this as well.
  6. I'm encountering the exact same issue. I was able to launch the Admin tool in Widows XP via VMWare Fusion, however.
  7. I figured that out, but since this server will be exclusively a FileMaker Server 9 Advanced box, I'd like to set the default page to go straight to the IWP default page. I realize that this is more an IIS config issue than FMS, but figured that other FMS users would have a better understanding than any non-FMS IIS users. I tried setting IIS to redirect connections to /fmi/iwp or /fmi/iwp/res/iwp_home.html>, but neither works. The first results in a redirection error, while the second gives me IIS's default "under construction" page. Essentially, I want to make it easier on our users to get to the server with a nice, simple URL. We have an old FMS7 box, and this seems to work fine there, but I have been unable to figure out the correct configuration to make it work on this FMS9a server.
  8. I have a newly installed instance of FMS9a on a Windows Server 2003 platform. The FMS Admin Console reports all systems are normal, and databases are accessible via remote FMP connections. The Admin Console Start Page appears to be working fine as well. However, I can't seem to get to the IWP page. Entering the server's DNS in a browser loads what appears to be an IIS "under construction" web page. I'm sure I'm missing something simple, but I can't seem to figure it out. Any suggestions?
  9. Does anyone have any advice regarding the recommended specs for FMS9a on a Windows platform? The official specs from FileMaker are somewhat ambiguous- Dual CPU/Core Duo. Where the minimum requirements list a Pentium 3.4ghz processor. The recommended specs can be read a couple of ways- would any dual CPU server do? Or any Core Duo dual CPU server? Or any Core Duo-based server? I've called FileMaker, and all they seem to be able to say is that the minimum is a Pentium @ 3.4ghz.
  10. My company is going to be rolling out a tool from our corporate parent that is based on FileMaker 6 (argh!). This tool will handle things like P.O.'s, employee timekeeping, etc. I'm looking for a way to extract certain bits of data from this FileMaker 6 solution so that the data can be used in a variety of other apps. Right now, I'm just looking to pull a list of job numbers along with a few other fields (client name, date job was created, date closed). Ideally, I'd like to set something up that can pull this information on a regular schedule, say hourly. This data would be stored in either a MySQL or a FileMaker 9 database, so that it can be used more easily across other applications. Does anyone have any suggestions, or maybe some references where I can find some information on how to go about doing this? Thanks!
  11. Ok, nevermind. I just found the "Sync" button in the Manage Database tool Fields tab. For anyone else who encounters this issue, go to Manage Database, select the Fields tab, choose the external data source you want to update from the drop-down menu, then click on the Sync button. Any table schema changes will be transferred to the FileMaker "shadow table", but you may lose any options you've set in FileMaker for a field if the same option isn't set for the field in the SQL data source. It's a one-way sync from the external source to FileMaker, apparently.
  12. I'm working on developing a app that uses FM to do some importing and data normalization, and then stores the resultant data in a MySQL backend for further processing. FM Server is on a Mac running OS X 10.4.10 server, and we're using the Actual Technologies Open Source Database driver. I have the ESS set up, and am able to read and write from/to it with no apparent problems. However, we've had to add fields to a few of the MySQL tables during development, and these newly added fields are not apparently visible to FileMaker. We added a table, and that table showed up in the data source list- it's apparently only changes to fields in existing tables that cause a problem. The only work-around I've found so far is to delete the data source from the FileMaker file and recreate it. After that, all of the new fields are visible in the various tables. The problem with this is that it breaks all the references to the ESS, causing a *lot* up editing in scripts and layouts. My MySQL guy seems to think that FileMaker is caching the table definitions, and just not refreshing them. Has anyone else run into this, and if so, have you found any better workarounds?
  13. Just as a quick clarifier in case it's needed, you set up the DSN via the ODBC Administrator (on OS X- not sure of the corrcect tool for Windows) on the server, then make sure that ODBC/JDBC is turned on in FileMaker Server. Now, create a new database, load it onto the server, connect to it, and from within that new database, add your external data source.
  14. Two quick questions on this: 1. I assume it is possible now with FileMaker Pro 9, correct? 2. Will FileMaker Pro wait for a stored procedure to finish executing, and return the results? Or does it simply execute the stored procedure and continue along?
×
×
  • Create New...

Important Information

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