kreg
2008-01-19 20:36:59 UTC
Here's an odd question. Would it make sense for Citrusdb to offer a way
to disable or turn off the billing portion of the program for weird
situations like I have below.
We have been using Citrusdb as a database to hold unique data about our
customers. We started using Citrusdb in our company which already has a
working billing system. The reason we started using Citrusdb, is
because our real billing system fails to function as a "customer
database". We can not easily adjust our real billing database to hold
the unique data about our customers. Data such as usernames/passwords,
additional requested email addresses, assigned static ip addresses,
business IP subnets, etc...
Citrusdb proved to be easily modified. All changes we make are by way
of how the manual suggests making our custom changes compatible with all
of the Citrusdb upgrades.
The unusual situation in this, is that we do not use any of the billing
features of Citrusdb. We bill with the as/400 system that was already
in place with our company.
Is there anything realistic about this approach? It seems our real
database is not realistically able to be modified to hold unique data
about our customers short of hiring professionals to implement changes.
And for an ISP like ours, changes occur often.
-Kreg
to disable or turn off the billing portion of the program for weird
situations like I have below.
We have been using Citrusdb as a database to hold unique data about our
customers. We started using Citrusdb in our company which already has a
working billing system. The reason we started using Citrusdb, is
because our real billing system fails to function as a "customer
database". We can not easily adjust our real billing database to hold
the unique data about our customers. Data such as usernames/passwords,
additional requested email addresses, assigned static ip addresses,
business IP subnets, etc...
Citrusdb proved to be easily modified. All changes we make are by way
of how the manual suggests making our custom changes compatible with all
of the Citrusdb upgrades.
The unusual situation in this, is that we do not use any of the billing
features of Citrusdb. We bill with the as/400 system that was already
in place with our company.
Is there anything realistic about this approach? It seems our real
database is not realistically able to be modified to hold unique data
about our customers short of hiring professionals to implement changes.
And for an ISP like ours, changes occur often.
-Kreg