|
..best idea would be to start talking with a bank.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
You should start by gathering requirements. Without those, any other consideration is meaningless. It doesn't matter what technology you use if you don't know what you're going to build.
This space for rent
|
|
|
|
|
True, without knowing data and what it should look like in the future it is impossible to predict anything.
|
|
|
|
|
Hi guys,
The app needs to have drag and drop function to build tool with workflow like visio for business users. Easy access for members via web or mobile devices. Internet may not available but mobile can sync data when internet is available.
setting up new application with the following architecture, so need your advice.
html5+JS on frontend on web, and swift on mobile.
Java - MVC webservices provide for both web and mobile front end.
bigdata on the back end.
you know any code generation should be used for Java?
Thanks,
AppNewbie
|
|
|
|
|
If you are new to application development, as your profile name suggests, then I think you are way over your head here, and should start off with something less complex. Just a thought...
|
|
|
|
|
|
Hello everybody.
I have WinForms app with WCF services selfhosted inside.
This app must redirect to some kind of ASP.NET app hosted on server. The user will fill a form and then will redirect again to the WinForms app. What technology to use and how the comunication between winforms app and server on response to bring back focus on winforms opened form ?
What are best practices?
Thank you in advance.
|
|
|
|
|
Windows applications don't have a concept of "redirecting" to a website, and websites cannot launch and control Windows applications.
Depending on what you're trying to do, you might be able to use a WebBrowser control[^] in your Windows application to open the website. You could set the ObjectForScripting property[^] to an object in your application, which would allow javascript on your site to call back into the application via the window.external object.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Another option would be to define fields in your WinForm and POST those directly from your application with HttpClient, rather than trying to move between browser and native app contexts.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Member 11891291 wrote: I have WinForms app with WCF services selfhosted inside.
I'm a little confused with this one. You have WCF services hosted in your WinForms app? Please explain further.
How about using a database that both your web app and winforms app communicate with. That way both are sharing the data that needs to be common in scope. Your WCF service(s) will facilitate this "sharing", as the same WCF service can be used with both the winform app and the web app.
Just a thought...
|
|
|
|
|
Hello,
Can you put a flat section next to a two point perspective section? In one part of my building it is clearer to show the ramps with the perspective angle. Is it acceptable to line up a flat section with a perspective one or do I keep them both flat?
Thank you
|
|
|
|
|
Sorry, I think you have come to the wrong house.
|
|
|
|
|
To clarify.
This forum is for Design & Architecture of software, not for buildings.
|
|
|
|
|
Use a different color / texture.
|
|
|
|
|
We are using UIP in our project.This an obsolete layer siting inside our application for controlling Session & Navigation management.applicaiton session level object are mainly store in UIP State and Navigation also done using it instead of intrinsic Session Object and Response object although below the layer those are only used. We want to migrate to new technology in phases. Can you please suggest the best approach and technology to replace UIP
|
|
|
|
|
It might help if you told us what "UIP" is.
Google thinks it's either "Usual interstitial pneumonia" or "United International Pictures", but neither of those seem to match what you're describing.
Wikipedia also lists "an open source implementation of the TCP/IP network protocol stack intended for use with tiny 8- and 16-bit microcontrollers"; but again, that doesn't seem to match your question.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
I am trying to build a Double Entry Accounting System from scratch.
I will use SQL Server Express 2014 for the database but I am totally confused about the optimal table structure.
There will be four principle account types namely Assets, Liabilities, Income and Expenses
Each transaction will have an effect on 2 accounts and both accounts can belong to same or different principal accounts.
I am seeking help for where to start and how much tables should be there?
My present design is like this:
1. Accounts Table
a.AccountID
b.AccountName
c.AccountType(which can be any of four or and sub account created under them)
d.TransactionID
2.Transactions Table
a.TransactionId
b.TransactionDetailsID
b.AccountID
c.TranDate
d.TranDrAmount
e.TranCrAmount
3. TransactionDetails Table
a.TransactionDetailsID
b.ItemName
c.ItemQuantity
d.ItemRate
e.ItemAmount
f.TransactionType (can be sale, purchase, receipt etc.)
Is this table structure good or it should be like something else?
|
|
|
|
|
Keys are wrong: 1d. remove TransactionID
Combine tables 2 and 3 into one ... you'll thank me later.
Add a "reference field" or 2 to the transaction for: invoice numbers; check #; P.O. #; etc.
"Quantities" are not part of an "accounting system" unless you are posting to a "statistical account" ... Not advised; that's what Inventory systems are for.
Accounts and transactions / postings: that's all you need for the operational system ... Everything else is informational.
|
|
|
|
|
Thanks for your reply.
1. I am planning to add the inventory master to that structure in future.
2. After combining tables 2 and 3, can we manage multiple transactions in 1 invoice?
Consider a scenario:
I have a client on whom I will make an invoice for services provided.
Now I have provided 3 services to him Namely
a. Bookkeeping Service
b. Reports Preparation Service
c. Business Consultancy Service
The Invoice will be having:
1. Date
2. Invoice Number
3. Client Name (which will be and Asset Account)
4. The Line level items (which are the services provided to him)
S.No | Item/Service Name | Duration | Rate per duration | Amount
1 | Bookkeeping Service | 1 year | $1000 | $1000
2 | Reports Prep Service| 6 months | $100 | $600
3 | Busin. Conslt. Srv. | 1 month | $500 | $500
Total : $1600.00
Applicable Taxes (if any): $0.00
Grand Total: $1600.00
Now each line level item will have an independent account mapped to it which will be credited and the client account will be credited.
On receipt of that invoice amount, Cash Account will be debited and Client account will be credited.
I need to allocate each receipt to an invoice as well as the client and calculating the closing balance.
I am a bit confused about making this design scale-able to accommodate new tables like inventory, payroll, taxation etc.
|
|
|
|
|
What you were modelling earlier was the "General Ledger": e.g.
[Account]->>[Trans]
What you are now getting into are the "Journals" (Accounts Receivable; Accounts Payable; etc.): e.g.
[Document]->>[Journal Entries]
(where a "document" can represent an Invoice, Sale (on credit or cash), Purchase Order, etc.)
The "document" contains "balanced" journal entries which are subsequently "posted" to the "General Ledger" (as "Trans").
(As I said before, consider what is "accounting data" and what is "tramp data" that belongs in its own subsystem; e.g. Payroll / personal; inventory "stats" versus $).
|
|
|
|
|
I get it now, I was quite confused earlier.
Basically what I need is the Invoice > Journal with ability to view Account Balances
What will be the optimal data structure to achieve that?
Should I keep only 2 tables? i.e.
1. Accounts
2. Transactions
Gerry Schmitz wrote: What you were modelling earlier was the "General Ledger": e.g.
[Account]->>[Trans]
What you are now getting into are the "Journals" (Accounts Receivable; Accounts Payable; etc.): e.g.
[Document]->>[Journal Entries]
(where a "document" can represent an Invoice, Sale (on credit or cash), Purchase Order, etc.)
The "document" contains "balanced" journal entries which are subsequently "posted" to the "General Ledger" (as "Trans").
(As I said before, consider what is "accounting data" and what is "tramp data" that belongs in its own subsystem; e.g. Payroll / personal; inventory "stats" versus $).
|
|
if (document.all||window.getSelection) {
document.write(unescape("%3Cbutton%20class=%22button%22%20onclick%3D%22return%20QuoteText%28%27"));
document.write("Gerry Schmitz");
document.write(unescape("%27%29%3B%22%20class%3D%22button%22%3E%20%20Quote%20Selected%20Text"));
document.write(unescape("%20%20%3C/button%3E"));
}
Quote Selected Text
|
|
|
|
|
|
The structure depends on your requirements.
2 tables are “optimal” if they meet all YOUR requirements and contain no redundant data; otherwise, it is not (optimal).
It is for you to decide. I presented possibilities.
|
|
|
|
|
I have done such work before. I agree with Prateek that combining table 2 and 3 is better. It results in de-normalised tables but the benefits you get in reporting are huge.
Plus I would strongly recommend that you have only one amount not TranDrAmount and TranCrAmount and make Credits positive and Debits negative. This makes calculating the net balance for an account (which is done very frequently) just a simple SUM statement on Table 2. If negative is is a debit balance and if it is positive it is a credit balance.
HTH
|
|
|
|
|
Whatever you do, make sure you have three distinct databases:
One for yourself,
One for your business partner(s), and
One for the Infernal Revenue Service.
That is the way to succeed in business!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
