|
|
| Subject |
|
| Default |
|
|
|
![]() |
 |
Developer and sales person required |
|
| Nigel |
reply
|
02 Feb 2010 18:01 |
|
|
|
|
|
|
|
![]() |
 |
We've moved |
|
| Nigel |
reply
|
01 Feb 2010 20:09 |
|
|
|
|
|
|
|
![]() |
 |
Why microsoft access? |
|
| kon |
reply
|
20 Aug 2004 13:48 |
|
I would like to know why you people using MS Access to develop a stock system, since there are a lot of advance software such as java, Visual Basic, C and others |
|
|
![]() |
 |
Why I used microsoft access.... |
|
| Nigel |
reply
|
20 Aug 2004 13:49 |
|
I originally developed the stock control system for a friend in Microsoft Access because they needed a ""simple"" system to track their sales and orders. Because of the libraries I've developed over the years it was a relatively quick job to build something useful.
Now the stock control system has many complex features but Microsoft Access still has benefits over other products. The benefits as I see them are:
- The product can still be quickly and easily developed if necessary.
- Most companies have a copy of MS Access and they can change TiNControl themselves. I have intended to make this product open source so that other people can develop it.
- The reporting tools in MS Access are second to none. I'm not the only programmer who tries their hardest to stay away from products such as Crystal Reports
As for your statement about advanced software... Why do you think that MS Access is not advanced? The Visual Basic for Applications programming language used (VBA) is exactly the same as in Visual Basic. There are also some nice features of MS Access that can't be replicated in Visual Basic.
Many IT professional are all too keen to put down MS Access as a non serious tool and it's mostly down to the fact that just about everybody thinks that they can use MS Access i.e. they have created a macro or used one of the wizards to display data from a table but have no idea how to program in VBA. In this respect MS Access is a victim of it's own success but it keeps people like me busy because there are so many hashed attempts at creating Microsoft Access applications.
I've always thought of Microsoft Access as having a similar reputation to plastic. Most people think of plastic as a cheap and nasty product but it's actually a very flexible product with a great many applications. It has gained it's low reputation because it's inexpensive and therefore used in conjunction with cheap low-end products which we then associate plastic with. |
|
|
![]() |
 |
Comparing Software development tools |
|
| Kon |
reply
|
22 Aug 2004 15:14 |
|
Hi Nigel, Thank for your reply. Actually I'm just a university student that interested in developing a stock system. I'm quite confuse and wonder which program I should use. I gone through your TiNControl, in term of functionality is quite good but the interface is not user friendly. I plan to use MS ACCESS to keep my database, and MS VB to create an interactive interface. What do you think? I need to justify in my report. So I would like to find out what is different between this two program, in term of functionality. Can you help me ? Give me some idea. Thank you. |
|
|
![]() |
 |
Comparing software development tools... |
|
| Nigel |
reply
|
23 Aug 2004 10:34 |
|
Thanks for your feedback on the interface of TiNControl not being user friendly. I would however disagree. It is difficult to make such a complex system simple to use and any stock control, sales and invoicing software is going to require a fair amount of practise before the user finds it easy. Still, I'll bear your comment in mind as there are always ways of improving the interface.
There are very few differences between the functionality available in Visual Basic and Microsoft Access. People use Visual Basic so that a program can be packaged up and distributed, something that doesn't happen for Microsoft Access solutions. Users will need a copy of Microsoft Access or the run-times in order to use a Microsoft Access front-end i.e. any forms, reports... whereas Visual Basic programs include the installation in the packaged executable and provided you've included all of the relevant dll's, activex controls etc. then no extra software should be required on the users machine (except a relevant copy of MS Windows).
If you're keen on using Microsoft Visual Basic to write the front-end in then why don't you use Microsoft SQL Server to manage the database instead of MS Access? MSDE (Microsoft SQL Server Desktop Edition) is a fully functional copy of SQL Server, the only difference being a restriction on the number of users (visit the free download page here). You can even use Microsoft Access as a tool for creating the objects in your SQL Server database (because the MSDE doesn't come with any tools such as Enterprise Manager or SQL Query Analyser) by creating a Microsoft Access Project (.adp). Check out the other messages on this website or search the internet for the advantages of using SQL Server over MS Access. |
|
|
![]() |
 |
Alternatively |
|
| Nigel |
reply
|
23 Aug 2004 11:39 |
|
| Why don't you use either VB.NET or ASP.NET for the front-end and SQL Server for the back-end? That way you'll be using the latest technologies which will be more robust in terms of performance and future developments. |
|
|
![]() |
 |
advantages of access over sql |
|
| luke |
reply
|
10 Sep 2006 14:24 |
|
| i have asystem that i want to run on sql coz currently it is working on access and it hs really gone slow ,can someone give me the advantages of sql over access and its configuration over a dormain.thanks. |
|
|
![]() |
 |
Re:advantages of access over sql |
|
| nigel |
reply
|
11 Sep 2006 13:57 |
|
Converting your system to SQL Server won't necessarily make it run faster. It may be down to connection types, the queries you're trying to run, indexes etc.
I take it that you're talking about a website. Is that correct? If so, can you give us the URL? |
|
|
|
|
[Add a new thread] |