Search results

Here is what I would do: Create a query using your current incident table. Pick 3 or 4 fields, that if put all together would make a unique string (Employee, Distributor, Store, Date Submitted for example). Then switch to sql view. (Top left icon on the ribbon). Add the word DISTINCT after...

Here ya go. I was a bit off on the code... Added a new field to store the Number. I also added a field to show you that you can simply format a field to display the number without actually storing it.

Correct! Correct Again! 99% of the time, I and most others, will use the Autonumber datatype as the primary key generator. This guarentees a unique number. Most of us have been there. I know I was when starting out with db programming. Once you get use to it...it will be second nature :)...

It's that 1% that will get you everytime. If there is ever a remote chance that a record can contain more than one of something, you are better off to err on the side of caution and create a separate table and use a relationship. Then the Distributors should have their own table. You can store...

Are the ODBC drivers for the correct FMP version? Other ideas: Can you export the tables into a text or csv file format? If so, you can export the data, then reimport it.

I dont have A2007. Can you save the database as a MDB file? Then I can take a look at it.

Ok, already see some issues: varAddress1 = Nz(Me.txtAddress1, Null) what you are saying is that if txtAddress1 is null, then it's null. Like I said, im cloudy when it comes to using quotes inside of quotes, so I'll show you what it should be using chr(34) strSQLUpdate = "UPDATE...

Then it shouldn't be Customer Name...it should be CustomerType. You can create a table with an ID and CustomerType. Then you should have a table with just the Distributor or Store. You can then store the ID of the Distributor or Store and use that to pull up specific data. This goes back...

I think you might be putting the cart before the horse. Let's analyize what data you want to store. Your main record is going to be the Incident. So we will start with that. Now lets examine what data you want to associate with each Incident. 1. Customer. Can the customer making the complaint...

I'm assuming that the problem occurs with the UPDATE sql statement. The syntax for an update query is: UPDATE tblName SET fieldName = NewValue I would imagine an error would be thrown up if you are attempting to update a field in the table that is datatype Long with a datatype Text. What...

Well, you should ask yourself, "Will I ever need to use the whole Tracking Number?" The reason is, you can store the whole tracking number, and format a text box to just display the number you want. In the case of not wanting to store the whole tracking number: I would put the code on the...

Sounds like you need to revist your table design. This is a classic Sales Database scenerio. Off the top of my head, you will need the following tables: tblCustomer CustomerID (Primary Key) Customer Info tblIncident IncidentID (PrimaryKey) CustomerID (ForeignKey) Other Incident Info...

I'm assuming that all the tracking numbers are the same number of digits. You can use the following code: dim sMyNumber as text sMyNumber = mid(me.TrackingNumber,17,12) This will tell access to go the 17th number and grab the next 12.

That is your problem then. The actual value that is stored in the field is a number, which is why you are getting the ID number. Lookups at table level are evil. A search for the evils of Table Level Lookups here on the forums will give you plenty of information why. To fix your problem...

Not sure what you mean by 'work'. Are you trying to put quotes around the value of varString so that they appear in the Sql statement? If so, then I believe so. I get confused by the use of single and double quotes inside of strings, so I generally have a function to do it for me. Public...

Hmmm....looking at your picture of the your query, there is a drop down field for the Employee name....but in the QBE, there is only the Schedule Table. Are you sure that it's not a lookup field? Open up the table in design mode and go to the Employee Field. Click on the tab labeled "Lookup"...

Is the field for Employee in your Schedule Table a Lookup Field?

did you do a debug.print on Left(strRowSource, Len(strRowSource) - 1)? Also, is strRowSource a valid Sql Statement?

When a text box is empty, it's a null value. You can use the nz() function to tell access what to put in when a null is detected. nz(Expression, WhatYouWantIfNull)

My bad..since there is a table that stores the TNE Numbers, you dont need the Junction table in the record source for the subforms. What you can do is create a text control on the main form. You can set the visible property to False to keep it hidden. (I called it txtTneNumHolder). Add the...