Access 2007, Visual.Net, ???

[lightbulb80]

I'M NEW TO DATABASE PROGRAMMING AND HAVE LIMITED PROGRAMMING EXPERIENCE. SIMPLE EXPLANATIONS AND TERMINOLOGY ONLY PLEASE

I've been tasked with producing two database systems at work.

1) A job ledger (currently excel)
2) A stock condition survey database

Question

For future proofing:

* what coding should I be investigating (I expected to use Visual Basic, I understand this has now given way to Visual.NET?)
* Should be upgrading to Access 2007?
* Where the best place for sample databases of this kind?
* What's an SLQ system? Should I be using this instead?

All help appreciated

 

[gemma-the-husky]

Whether Access is right for you depends how big/how many users the system will have.

Access is good for systems up to 2Gb in size - despite what people say, it is very stable, and performs well.

Access is multi-user out of the box - theres no limit to the number of users - it depends on what they are doing - typically it will support 10 or more, no problems.

Access uses a form of VB called Visual Basic for Applications (its special to access, and slighltly different ot the vba used in excel code modules). You could use Visual Studio etc, to interface with an Access database, but then you would have to duplicate in code all the nice interface stuff that comes with Access. Stick with Access.

I actually prefer Access97 (note that A97 will only handle databases of !Gb - its still plenty big), as it is quicker and needs less memory. Later versions do add some extra facilities, but nothing you cant live without. Access 2007 is now somewhat different - Not sure what everyone's experience is of A2007

I think you mean SQL, not SLQ. SQL is more secure, and processes differently - you can always upsize to SQL later if necessary.

-------
look here for samples, access ships with some demo databases - but your requirements will probably mean there isnt a standard solution that fits what you want exactly.

 

[Rabbie]

I think you mean SQL, not SLQ. SQL is more secure, and processes differently - you can always upsize to SQL later if necessary.

-------
look here for samples, access ships with some demo databases - but your requirements will probably mean there isnt a standard solution that fits what you want exactly.

I agree with Gemma. Just to clarify on SQL. This is the language used to store queries in Access and in other Database programs.

Microsoft has a product called SQL Server which can be used to run your back-end database when it grows too big for Access. I would develop initially in Access.

 

[complex]

If you want some information on databases based on .net technology look here,
hope it helps.