Paul Clapham wrote:Your database is going to require a server, there's no getting around that. But there's no reason to be concerned, either. You can (and should) set it up so that it's only accessible within your local network -- this is the standard way to set up a database.
If you plan to write a desktop application for a sales system, well, that's sort of an unusual thing to do now. Desktop applications are very out of fashion. But they are still possible.
As for do you need Oracle SQL, no you don't. There are lots of SQL databases available, Oracle is just one of the possibilities.
Paul Clapham wrote:The terminology is confusing you. A "server" can (and often does) mean a computer on which you run various applications whose purpose is to serve other applications. And it can (and often does) mean one of those applications.
For example a "web server" can be an application which responds to HTTP requests by sending back web pages as its response.
None of this has anything to do with Java, really, except that you could write a server application in Java if you liked.
As for desktop applications written in Java, you could use Swing or JavaFX. However it doesn't seem like there's a lot of people using those features to write client software nowadays. It's much more common to use something like REST-ful web services to connect to the server. Of course you could use Swing or JavaFX to use those web services but what I mean is, it's more common to use JavaScript in a browser to do that.
And as for ".exe", yeah, you could do that in Java with some extra work but it's unnecessary and just provides another source of problems for you to stumble over.
omar tawfeek wrote:thats great but how can i upload my application and its database on a server is there any tutorial out there teaching me how ?
Paul Clapham wrote:
omar tawfeek wrote:thats great but how can i upload my application and its database on a server is there any tutorial out there teaching me how ?
You aren't going to do that. The server is a computer so you are just going to sign on to that computer (as an administrator, hopefully) and install the database.
And if you're going to write a desktop application, then there's not much point in having it on the server. It needs to be on the computers which belong to the people who are going to use it.
Again, none of this has anything to do with Java. It's just basic computer network management.
Paul Clapham wrote:The terminology is confusing you. A "server" can (and often does) mean a computer on which you run various applications whose purpose is to serve other applications. And it can (and often does) mean one of those applications.
Education won't help those who are proudly and willfully ignorant. They'll literally rather die before changing.
Paul Clapham wrote:Actually... instead of having somebody try to explain networking to you in bits and pieces, you could try reading a book instead. Here's a good one for beginners: Networking For Dummies.
You may find tutorials online if you care to search but the field of networking is large enough that a book is a better source.
Paul Clapham wrote: Sure, in a professional context the two things will be running on different machines
Education won't help those who are proudly and willfully ignorant. They'll literally rather die before changing.
This is awkward. I've grown a second evil head. I'm going to need a machete and a tiny ad ...
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
|