Passa al contingut principal

dbswdevelop

Hi all.
Mi name is Tomas Eroles.

Professional

At this moment I'm unemployed, and, of course, available for a job on programming, also for freelance projects.
My main skill ara databases and develop software with MS Access and VBA (I'm an expert using this tool), but what matters is to know about programming and analysis. As a (almost) Systems Engineer, I may learn others languages.
I know VB.NET, HTML+PHP, GAMBAS, and other programming languages, but I'm not so good than with Access.

Personal

I was born in the city of Barcelona in 1974, and moved around 200 km to south with my family when I was 5, to the nice city of Vinaròs.

I'm finishing my studies on Systems Engineering.
I'm married, and we have two little daugthers.
I love computers, technology, travel with my family, and cook.

This is a blog about Databases, Software, and Development.

The main tag will be MS Access. I've been using this software since 1994, after some years using the xBase products (dBase III+, dBase IV from Ashton-Tate and Clipper from Nantucket).

I will appreciate your comments, and I will try to answer them.

Comentaris

Entrades populars d'aquest blog

How to manage data in forms using only VBA. And why. How to use System Windows and stored files.

Introduction Hi all! Today's subject is about how to use a form to manage data using only VBA. As you know, manage forms with data in Access is very easy, practical, and may be done from the first minute. When you build a data source, a table or a query, you may create a form linked to them. This means that Access will do all the tasks related to manage the data, and when the form will be opened it will show those data automatically. This is very useful, especially when the user is a beginner, or just when neither the time nor security are really important. I will try to explain myself better. When we use the wizard to build a form, it fills automatically the RowSource property for the form, and the same for each field. As I said, this is useful, but may have some problems: When there are a big amount of records (more than 250.000) and/or a big amount of fields, the load process may be a little bit slow, and also if the form shows a large set of records or it has to sel...

Table and form for window Options in your application

Introduction Today I will explain how to do an Options dialog box with parameters for your application in MS Access. An options window is a simple dialog form. It may be linked to a table, but I prefer to do it using VBA, to have a more professional look and a very good maintenance. This post is organized in six steps: the table, the form, the records, the code in a module, finishing the form, and the code for the form. At the end of this post you may download a small Access file with the form options, the table and the code to manage it. First step: The table For the table, I usually create a table with three fields. The name of the table is Options: parName (text, 50, Primary key): the name of the parameter parValue (text, 50): the value of the parameter Details (text, 255): a brief explanation text field to have information about the field, like a comment. Later in this example we will see that there are different types of values, but the field is always a text fiel...

Use of listboxes as a data summary instead data forms

Hi all This post is an extension of the previous post ( how to develop a carousel ). Here I will show how to manage a summary form linked to a detail one, in order to show data and detail them. I want to clarify that this is not "the way" to work with access, this is "a way". This is the way I use. After been developing Access applications, I've found this is a good solution, and I use it almost always. I will improve the previous example, the used cars seller adding a new form. The new form has a listbox and some buttons (add, delete, duplicate and modify) to perform those operations. All those operations are solved using VBA, as you may see. The new form is named Main. You may see in the next screenshot I've added new records. Once the form is loaded, the data are stored in the listbox using the Form_load event. The objects are named as follows: Button Add is named cmdAdd Button Duplicate is named cmdDuplicate Button Delete is named cmdD...