Search results

Thanks for the help. I used plog's second suggestion, of creating an autonumber field in a temporary table to import the data and then using a repeated query to fill in the data.

In order to compute commissions I need to read data from a spreadsheet provided by the customer. Unfortunately, the customer does not understand the first normal form and is not showing repeated data. Sid Harvey Sid Harvey Branch Sid Item 0004 BROOKLYN,NY (0004) NY SPE-EZ5E-CS...

When you talk about redirecting the funds you are taking fundamentally socialist point of view that the money "belongs" to the government. Each government program stands on its own, if the government spends excessively or improperly, that money should go back to the taxpayers not be used to...

Your support for a tax increase for Social Security is interesting. By saying general revenue should be used to pay for Social Security you are changing Social Security from a mandatory pension program to a welfare program for old people with a far greater degree of income redistribution. Your...

Current US law does not require refugees to have a visa or to have come directly to the US to apply. The difference between illegal and legal immigration is simply a matter of government policy which can be changed. The US has a large demand for labor and that attracts immigrants. The US...

That seems like a dangerous thing to do, as the user could scan twice by mistake. Especially for tracking medication, the user should be forced to enter the quantity. I wouldn't even use a default, what if you need to audit your inventory for controlled substances.

Note that most of those crossing the border are not coming illegally. They are turning themselves over to the border patrol and applying for refugee status in accordance with US law. The largest group is coming from Venezuela, where a "Socialist" government destroyed the economy and persecuted...

Import Drawback Receiver is a local Access table. Combined_Part is a query. Part Lines is a linked Access table. Based upon the references that were mentioned, it seems that a cancatenate operation in query will always cause truncation.

I am using an SQL Server back end. It seems that the simplest solution is to split "Body" into 2 fields. This allows me to use my generic send e-mail function, as opposed to creating some customized code. I have tested splitting and everything worked. Fortunately, I don't have a business need...

There is an intermediary, but the truncation is visible in the query itself. SELECT DISTINCT dbo_Receiver.ID AS Receiver_ID, dbo_RECEIVER_LINE.LINE_NO AS Line_No, dbo_Purchase_Order.ID AS PO_ID, dbo_Purchase_Order.VENDOR_ID AS Vendor_ID, dbo_Vendor.USER_5 AS [Vendor Name], dbo_Vendor.COUNTRY...

Many of the fields are from an external database that I can't change the field type for. I tried using cancatenating a long text field at the start of the field, but it did not help. Neither did changing the field type with CVAR, either for the first element of the field or the entire field. I...

I have query that is being used to generate the body of an e-mail. Sometimes, the result should be more than 256 characters. However, when the query is run, the value is truncated. Is there a way of having a query generate a result that is more than 256 characters?

You will need 2 queries. The first query selects the max Seatime_ID for each Crew_ID. The second query links the first query to the original data to pull up the dates. Queries referencing other queries is a useful technique.

It looks that you are trying to track inventory in some fashion. Lots are being received, moved and I assume shipped. You need to have a table of inventory transactions. Once you are tracking that information, you can determine everything else with a query.

You are doing this backwards. You should have a table of all inventory transactions. When an inventory transaction is created, you should then update the other fields. If there is a problem, you always go back to the table of inventory transactions and determine the correct values.

Just as you thought, there was a field that still had null values, even though the default was set. Fixing that resolved the issue.

Access is recognizing the primary key. It works as long as I select specific columns but fails if I use the "*".

Last night, I needed to rebuild my database by creating a new database and copying all objects into the new database. I am now receiving the "This record has been changed by another user since you starting editing it" error when I edit a specific table that is linked to SQL Server. 1. If I go...

A period would be a bad character but in practice that it not likely to be an issue. The problem is inconsistencies in the source document being transcribed, which sometimes has dashes and spaces.

The length of the values can vary. Even if the values had a fixed length, I would be uncomfortable using a numeric field with something that is not really a number. It could cause future problems if somebody thought is was really number and didn't pad with leading zeros.