WPF or ASP.NET for creating a simple multiple access application? : <p>I have read some related articles but didn't find a perfectly fitting answer to my questions. </p>

<p>I need to create a simple application to perform basic accountancy related operations. The requirement is such that multiple users (in my case up to 5 people) in the same LAN need to be able to work on the same database from their machines. As the application is going to be simple (basic add/subtract operations and storing the results in the database) I wonder whether I need to use ASP.NET or I can use WPF implementing basic communication interface (WCF seems to be a good helper) as I was working mostly with WPF and have only little experience with ASP.NET. To keep simple again, I decided to use SQLite instead of RDMS (like MS SQL Server or MySQL). I read <a href="https://www.sqlite.org/whentouse.html" rel="nofollow noreferrer">here</a> that it is better to use client/server DB for my purpose but I believe that the scale of my project is so small that eventual latencies will not bother me. What I need to know is whether it is wise to use WPF with SQLite database as a shared network resource and accessed by other users or it is better to dive into ASP.NET for this reason. </p>

<p><strong>To sum up my requirements:</strong></p>

<ol>
<li>The application is very simple in terms of performed tasks (only basic accountancy related operations),</li>
<li>Simple database (SQLite is my choise),</li>
<li>Multiple access but only for few people (up to 3 or 5 people),</li>
<li>The users will be in the same network,</li>
<li>I do not bother about eventual latencies</li>
</ol>

<p><strong>My doubts are:</strong></p>

<ol>
<li><p>In my case - will it be wise to use SQLite concurrency embedded mechanism if the traffic is very small (only few people)? In the SQLite docs it is stated that basic concurrency is handled in terms of multiple reading access and only single write access at the same time. However I have never used concurrency in SQL so I would need an opinion of somebody more experienced in this topic,</p></li>
<li><p>Is it better to learn more ASP.NET to create a basic client/server app (I would prefer SQLite as DB again) than implementing WPF with some network related stuff like accessing the shared SQLite file or using WCF to achieve the same? I mean, isn't it complicating everything too much by prefering WPF over ASP.NET? If the application was supposed to be big, scalable etc. I would definitely stick to ASP.NET but in the case of simplicity of the project and simplicity of creating WPF application using C# and XAML I doubt which technology to use in my particular situation to keep simple in the terms of development.</p></li>
</ol>

<p>If there is a better solution than the stated above, please mention it (I would prefer to stick with C# but I am open to other suggestions).</p>
