Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Multiple companies (database) and SDT
Message
From
27/03/2010 15:58:17
 
General information
Forum:
Visual FoxPro
Category:
Stonefield
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01457601
Message ID:
01457630
Views:
44
>>What would be the best way to make a software multi-companies. I use Stonefield Database Toolkit. Would SDT make things easier?
>>
>>Let me give you more details and why I see SDT involved in this.
>>
>>Multi companies means multiple copies of the database that I have right now.
>>
>>For example right now in my code I do "Set database to..." and that's it. My application runs fine.
>>
>>I'd like to give the possibility to the user to specify which database (company) to use.
>>
>>SDT is letting me do something really nice and that is to update a customer's database structure automatically. That means that whatever changes I do they go into metadata files. When I copy those files on a client's machine his database structure is adjusted to reflect the new structure I have on my computer.
>>
>>I guess that multi-companies would be done within the application. That is the user wants to create a new company then I create a copy of the database to another DB and in the future when the app is launched I ask which company needs to use the app. That's why I'm wondering if SDT could still manage this multi-companies thing.
>>
>>So I'm wondering what would be the best moves to make my application work for multi-companies.
>
>I misunderstood what you are trying to do when I replied to your message in another forum. I am not sure the SDT would help you; although maybe Doug will chime in and provide suggestions. My guess is that what Michel Fournier does is what I would do; have a field in each table defining which "database" the record belongs to. And then whenever you retrieve records from a table you would have to filter out based on the user selected company number (I would make the field INT and have each company ID to be a number).
>
>HTH.

All in all a good suggestion I will consider it before making the final decision.
*******************************************************
Save a tree, eat a beaver.
Denis Chassé
Previous
Reply
Map
View

Click here to load this message in the networking platform