I have two databases in two different folders. One is my Customer Activity database. One is my Stove Models and Products database.
Originally I was developing these as separate applications but am now considering merging them into the same application.
I like the idea of having them as separate databases but now I want to share the data from the Products database with my Customer Activity application to create estimates and keep these estimates in a table with the Customer Activity application.
I am wondering which way is best. Should I merge the two folders and copy all files from each database application into the same folder and then continue developing my applications using only this one folder? Or, can I just keep the two folders as they are and add the tables I want to use from the Products database into my Customer Activity application?
Seems to me I got some warnings about adding databases from foreign folders when I've played with this before. What are the disadvantages to keeping the databases in two separate folders? If I want to have both a small Products application and the more complex Customer Activity application won't it be best to keep the simple Products databases in their own folder? If I want to copy the Products application I can copy it's folder. If I put it all in the same folder I will have to copy a lot of files I won't need for that simple application.
I suppose I should just charge ahead and see what happens. I am inclined to leave the databases in two separate folders and add the needed tables to each application as needed. But I don't want to make a mistake in design that I will have to redo later, when I learn more about what the heck I am doing.
Anybody have any tips on how I should do this?
Thanks,
Sean Kennedy
(part time developer, full time business person)
Originally I was developing these as separate applications but am now considering merging them into the same application.
I like the idea of having them as separate databases but now I want to share the data from the Products database with my Customer Activity application to create estimates and keep these estimates in a table with the Customer Activity application.
I am wondering which way is best. Should I merge the two folders and copy all files from each database application into the same folder and then continue developing my applications using only this one folder? Or, can I just keep the two folders as they are and add the tables I want to use from the Products database into my Customer Activity application?
Seems to me I got some warnings about adding databases from foreign folders when I've played with this before. What are the disadvantages to keeping the databases in two separate folders? If I want to have both a small Products application and the more complex Customer Activity application won't it be best to keep the simple Products databases in their own folder? If I want to copy the Products application I can copy it's folder. If I put it all in the same folder I will have to copy a lot of files I won't need for that simple application.
I suppose I should just charge ahead and see what happens. I am inclined to leave the databases in two separate folders and add the needed tables to each application as needed. But I don't want to make a mistake in design that I will have to redo later, when I learn more about what the heck I am doing.
Anybody have any tips on how I should do this?
Thanks,
Sean Kennedy
(part time developer, full time business person)
Comment