Hey folks

Can I combine existing seperate database files into one master database?

I have to get together an asset management system and I wanted to be able to give the Users, Hardware Assets, and Software Assets unique databases. I tried making a master list that contained all the fields I wanted for the three databases and then created three layouts accordingly. The problem was that I would create a record for a piece of hardware in the Hardware layout and then create a record for a user in the User layout but the two layouts don't share the same fields and when I went to enter a new user record I would mistakenly be adding the information to what seemed to be an empty record but was instead a hardware asset that wasn't showing any fields in the User layout...(phew! I'm just tired from re-reading that!)

So I ended up just creating three seperate database files - Software Assets, Hardware Assets, and Users - so now I have three windows open at a time when entering data which can be difficult to manage. I was wondering if there was a way to combine the three seperate files into one master list? Perhaps I should go back to the original master database and I was just not building it correctly?

Thanks for any help...

Use FM Migrator to change files into tables of one file. It's only $100.

I downloadsed the demo of FMPro Migrataor and tried it but got the most obtuse and confusing output that I could do little with. it was easier to keep three seperate databases. I'm on a Mac and haven't seen a lot of positive feedback out there about it on the Mac side.

So is there no way to do it in Filemaker itself?

I didn't think it was available for the Mac.

There's a version 2.35 on their site...

http://www.dotcomsolutionsinc.net/downloads/demo_software/index.html

It requires just a little knowledge of Perl.

After I figure out Filemaker, maybe I'll move on to Perl...

But back to my original question(which I'm guessing is no):

Is there anyway to join these databases together within Filemaker Pro 7?

I don't know why transpower sent you on that wild goose chase. It looks like you're in need of a better design, not a tool for combining separate files.

Since Users, Hardware Assets, and Software Assets are all separate entities, they should be defined in separate tables. This can be done within one file by going into the Tables tab in the Database Definition dialog. Create the tables, then create the fields for each in the Fields tab. By the way, FM Migrator and FM Robot can add these tables from exsiting separate files, but it's really not that hard to just retype the fields (using exact spelling, in creation order) then you can simply copy and paste existing layouts from the old files into layouts based on the new tables in the new file.

There's a good chance these tables should be related. Software is usually installed in specific machines, and Hardware assets are often assigned to specific users. In my asset management system, I have computers assigned to specific rooms, and staff also assigned to specific rooms (this way I don't reassign the computer when the staff in a room change.)

How you decide to relate the tables depends on your business rules, but you might have a UserID field in the Hardware Assets table as the match key relating to the UserID field in the User table. And a Hardware Serial# field in Software Assets that matches which computer a particular Software Asset is assigned to.

I know you were thinking about making a master list, presumable holding all Software and Hardware Assets together. I would recommend against this as these usually have different fields and are related to different things. Instead you should design your system with navigation buttons that can easily jump from table to table, pulling up related information as you navigate. This way you can go from the Users table, click a button on a Hardware Asset line (in a portal) to pull up the related Hardware Asset. Then on the Hardware Asset detail layout, see a portal of all the Software Assets assigned to that Hardware, and click a button (in a portal) to jump to the detail layout of the related Software Asset.

Isn't it an improvement that FM7 allows multiple tables in a single file? I started off with FM7, so I dont know about the previous versions. I had 5 separate files that I decided to combine into one database as different tables. Its been worthwile for me. Scripting is definitely simpler that way.

CTLS

In general, it is simpler to use fewer files. But for Kayos' three tables, it's not worth buying a program to combine them.

Yes. I did it manually.

CTLS

Ender

Thanks for your input, that was exactly what I was trying to do it. I thought it could be done but didn't really didn't know what to look for.

Off to build a database...