April 21, 2014 at 2:34 am
front end = VB.net desktop app frame work 4.0
language = VB
database = sql 2012 (express edition) for client end
Its not web-front end its client based (windows form application)
I wana give full functionality from my Client software (Insert , update , delete, select etc)just like Tally
I am not planning to give web functionality at this time .
even if i do i will use web front end just for reports not insert or updates from web portal
May be i cant explain my self so i am giving an example
suppose i have a customer having 5 branches and every branch has 5 computers all working on my erp system
every branch has 1 database server and 4 database clients
i wana connect all branch database servers so that all branch servers have same database
now lets say i have 200,000 customers all with branches and all with branch servers how will i connect all those databases
every customers database has nothing to do with others customers database
i am developing and ERP system i already have more than 1k clients at the moment
i am planning to expand my erp system
but i need online solution in my software
so that my clients can input data from any where just like quick book or tally
i just want any information regarding this topic
whether should i use replication and what would be the complications
Another question which i wanted to ask should i make different databases for each client and use replication or single database for temporary data point and then rerouting it to other clients
or just live connection
or any thing else
thanks
April 21, 2014 at 2:51 am
Information is not sufficient to provide any conclusion. You need to have web based front end to input data. What about the backend? How is your database design? How users do entry to database?
If replication what kind of replication model fit to your requirement?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 21, 2014 at 2:58 am
sorry for incomplete data
front end = vb.net
database = sql 2012 (express edition) for client end
need to connect my desktop application so that it can input data online
April 21, 2014 at 3:37 am
Still not enough information.
Did you use vb.Net to develop a Web-Frontend or is it a client based solution?
What online functionality will you provide (full functionality or just part of it)?
Do you have a detailed and profound security concept to separate the different customers as well as protect the data from any kind of intrusion/manipulation?
Be aware that allowing external access to an ERP system usually is not a recommended scenario...
I strongly recommend to separate the Web functionality from the original ERP system. Not only in a separate database on the same server but on a separate server. Harden the connection between the two as much as possible. Transfer the data to the ERP system using "bullet proof" stored procedures. Be suer you know how to eliminate the risk of SQL injection.
Always keep in mind: As soon as there's a Web site to get acces o your system, you no longer have only the customers you know of but also a ton of people interested in getting the information you stored...
April 21, 2014 at 10:26 am
Did you use vb.Net to develop a Web-Frontend or is it a client based solution?
Its not web-front end its client based (windows form application)
What online functionality will you provide (full functionality or just part of it)?
i wana give full functionality just like Tally
Do you have a detailed and profound security concept to separate the different customers as well as protect the data from any kind of intrusion/manipulation?
Thats another question which i wanted to ask should i make different databases for each client and use replication or single database for temporary data point and then rerouting it to other clients
Be aware that allowing external access to an ERP system usually is not a recommended scenario...
some of ERP systems are already doing it
I strongly recommend to separate the Web functionality from the original ERP system. Not only in a separate database on the same server but on a separate server. Harden the connection between the two as much as possible. Transfer the data to the ERP system using "bullet proof" stored procedures. Be suer you know how to eliminate the risk of SQL injection.
I am not planning to give web functionality at this time .
even if i do i will use web front end just for reports not insert or updates from web portal
And i am well aware of sql injection
Thanks
April 21, 2014 at 11:02 am
If it's client based, how do you plan to expand your software
so that my clients can input data from any where
?
That's contradictory to your client based installation.
At this point I step back. To me "Tally" means a numbers table and I don't think I'll spend the time of a product research to figure out what you might be looking for.
As a side note: Just the phrase "some of ERP systems are already doing it" doesn't make this concept more recommendable...
April 21, 2014 at 11:23 am
Thanks litz for ur time
may be i am unable to explain my self so i have updated my question with an example. Please check it
April 21, 2014 at 12:00 pm
Honestly I think you should hire a consultant to help you design your system. There are items in your list that contradict each other and many that sound as though you are unfamiliar with the technology and how these things work.
Maybe webservices would be a help here?? hard to say based on the very limited details in your posts.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply