Upgrading & Migration

I converted my files. I use containers to hold a background color on all layouts. The background no longer fills the container field - the right and bottom shows white instead of the color. I tried repasting the color swatches into the container field but it doesn't solve the problem. Graphics format is set to reduce/expand and center-to-center. I tried adjusting this and nothing is working. Any ideas? It looks terrible and I have a presentation this afternoon showing the new 7. Does anyone know a fix for this? Linda Version: Developer v7 Platform: Windows XP

I've been toying around with FM7 for a little bit now, and I'm a little confused about the way scripting is in Fm7... If I'm running a script that effects two tables, is the only way to switch the scope by using a Go To Layout (for Set Field etc)? Is there another way I haven't found yet? P.S. FileMaker 7 is a great great improvment, I've been excited since I saw the technical preview. FM 6 and below was a pain i the neck! Version: v7.x

We have just converted some of our files from version 6 to version 7. Each file has about 50 relationships. This may sound like alot but we are running an entire Insurance company using filemaker. The new relational graph is an absoulute NIGHTMARE!! What was once managable is now un-managemanable. Has anyone had this same experiance? What were they thinking ? Stu Version: v7.x Platform: Windows XP

I realize I'm not the only one confused on how to fully take advantage of the new relationship model in FM7 but I hope someone can provide some insight. I understand relating Invoices and LineItems -- or Customers with their addresses, etc. but how far up the chain should these databases be combined? Staff also relates to Customers and I'm unsure whether to combine them also. If you think about it, EVERYTHING is related to the one single company and could be combined! I'm specifically confused on my existing Preferences and Graphics databases - which hold buttons and backgrounds. If I combine everything into one model, will it be too much for FM7? In FM6, I have 1…

Hi, I am about to do a new project for a mid sized company that due to Fm 7 Server not being release yet, has not upgraded anything to FM 7 yet. They want me to create and add to current 5/6 systems. I was wondering if anyone has found any methods for making 6 databases easier to convert to FM7 when they upgrade. Version: v7.x Platform: Mac OS X Panther

Hi, I've been skipping through the trial version of FM7 and have come across the option to add tables within the same database. I can't find any real info on this in terms of what is possible with this option. I currently manage a 30-40 file database in FM6 and the idea of combining some of these files could be interesting in several areas for me. Has anyone played with this and know how this works? Jim de Kort

1. I just created a separate date ("//") and a time ("::") in the body of a layout. I formatted the date to be Thursday, December 25, 2003 and the time to be 1:09 PM. I then cut and pasted them both to the header and when I looked, the date was completely screwed up, with a "1" as the 1st separator, a 2 as the second separator and a 3 as the third, so the today's date reads Tuesday1March22332003". This does not happen in FMP5. 2. While importing data from another table, I found that if you move a field in the import list using the CNTL-arrow key combination, any link you have already established gets moved one field up or down (depending on which way you are arr…

I've quickly perused the technical brief on migrating existing fp3 and fp5 solutions to fp7: http://www.filemaker.com/upgrade/techbriefs.html But I'm wondering if anyone has actually tried it yet with a fairly large solution (10 or more files), and what were the results? P.S. I'd try it with my current project, but I'm so busy trying to get real work done I haven't had time to download the trial version. Just when I want to play, I have work to do. ::sigh::

From a forthcoming document on Conversion/Migration: Regardless of your scenario (except for very simple solutions), it is wise to anticipate converting the solution numerous times. It is most efficient to do pre-conversion analysis, dry-run conversion, and post-conversion testing. Then go back to the pre-converted solution, re-analyze, make more modifications, and reconvert. Repeat this process until the efficiency of pre-conversion tasks has been exhausted, and then do a final conversion and make necessary changes which can only be made in FileMaker 7. Plan well, and follow the plan. Be methodical. Expect to change course or discover things during the process …

Boulder, Colorado - March 18, 2004 - New Millennium Communications announces FMrobot, a tool which automates the process of creating tables and fields in FileMaker 7 databases. The initial release is a commercial beta version for Windows only. The full commercial version is expected by the end of March. A Macintosh version is also planned. FMrobot can be downloaded for evaluation and can be purchased at http://www.newmillennium.com. With FMrobot, you can consolidate tables from one FileMaker file to another, as well as effectively duplicate tables within a FileMaker 7 file. You can also build a "library" of "template tables" which you can transfer into any ne…

How can I convert a fm6 database with many seperate files into one (1) fm7 database file? Version: v7.x Platform: Mac OS X Panther

When we convert password protected files from 6 to 7, the new password prompt pops up with the user name as the account, and the password blank. To get into the file, we must clear the account field and enter the password. The file will open that way only. When we open the define accounts and privileges, the account names are the original passwords and the privilege sets make no sense whatsoever. When we try to edit an account, there appears to be a 20 character password in already. What gives? Version: v7.x Platform: Windows 2000