Recent content by plog

1. Non-null "Nulls". Your eyes cannot be trusted to see a null value. Just because it looks like there is no data in a field, doesn't mean it is null. It could be an empty string (""). It could be a weird character (line return, tab, something else). To a computer all those things I just...

You shouldn't have fields named after days of the week. Your adding bandaids on top of bandaids with the issue you posted about. The real fix is to normalize your data properly, then just bind forms to them so they handle the data adding, updating and deleting.

Why do you want it like that? Typically a 1 to many relationship (as in your 1 Customer to many Services) is done with a subform that scrolls vertically like so: ServiceNumberServiceType 1abc 2def 3ghi If you have more services to add to a customer, just keep adding new records...

What you have now is a 1 to many relationship. Your existing table is the 1 and that new table I prescribed is the many. With forms you use a main form to display just 1 record from the 1 table and a subform to show as many records as needed from the many table. Here's good documentation for...

Data, always start with data. The process of setting up your tables and fields is called database normalization: https://en.wikipedia.org/wiki/Database_normalization Presumably some sort of system(s) currently exists for this. It might be in a few systems--an app supported by IT, some...

Can you upload a copy of your database? If not, complete the Relationship tool, take a screenshot and then post it here. Before you move on to forms its best to make sure your tables are correct. I just don't want to miss any other issues that will mean re-redesigning the forms.

Agree with DBguy, you need to fix your tables not band-aid this. You are storing data in field names, that is an incorrect way to store your data in a database. A general rule of thumb is that field names should be generic (CompanyName) and not specific (Geico). So instead of a field for every...

Ha ha. Assumptive 'woulds' and 'shoulds' always puts a smile on my face. Not saying you are wrong, but in my experience data reality very rarely matches peoples assumptions about their data. And very often to poor results. SELECT Customer_ID, Order_Date, Order_No, Item_Code FROM...

You need to put aside this issue and focus on your real problem--you haven't set up your tables/fields properly. That process is called database normalization: https://en.wikipedia.org/wiki/Database_normalization Give that link a read. Then google a few tutorials, then apply what you have...

Most likely this is because that's what's in the data. Pretty confident it has nothing to do with your SQL. This probably gets fixed by putting a Trim() around each field of the SELECT.

Your database seems simple enough, but there's a few things I don't understand. 1. Only one item goes to an invoice? That seems different from every other invoicing system in the world. Usually a system like this has 4 tables--Clients, Items, Invoices and InvoiceItems. That way an invoice...

Doc doesn't want to belabor the issue, but after your two recent posts it seems someone has to: 1. Type is a poor name for a field. It is a reserved word which will make coding and querying more difficult later on. You should prefix with a word that the type represents (e.g. SalesType...

I only use unbound forms for menus. If I want the user to act on the data (create, update, delete) I use bound forms. Even if I want the form to be read only but I wanted to display a lot fields from a datasource I would still use a bound form, but just disable everything. Bound forms are easier.

When you have ties there's no predicting how its going to sort. If you want to ensure the same sorting you should add a unique field in addition to the date one.

Also, who cares? Why must your numbers start with a particular value? Autonumbers should only be unique. If you have that they will serve their purpose. If you are using them for another purpose other than uniqueness, you shouldn't. So, what exactly is the issue if they don't start with a...