Search results

If you want to keep it simple, just try to open the table recordset: 'Check if an ODBC connected table is reachable Function IsODBCConnected(TableName As String) As Boolean If Not TableExists(TableName, True) Then Exit Function Dim rst As DAO.Recordset On Error Resume...

Looking at the database you posted several posts earlier: if you select the query 'ZooMobile Cost Query' and then via the Database Tools click 'Object Dependencies' you will see that the forms you mention depend on this query. Open the query in SQL mode and you will see that the first lines...

The other way is simply using less joins, so Access can handle it better. Many values are now stored directly in the main table instead of a look up table, implying increased redundancy.

I went with another (less space-efficient) way which performs much better. Thanks all for your input!

If you only want to use SQL try the following TRIM(REPLACE([Title] & " " & [Firstname] & " " & [LastName], " ", " ")) AS FullName in your query.

This also often occurs when the form is still trying to order or filter the dataset on that specific removed field. Remove these references in the properties of the form.

For your first problem, the following query works (unfortunately you do not have too many examples in your database, so it's hard to check the correctness). I'm pretty sure there might be a better solution. SELECT D.PROVIDER_ID FROM ( SELECT C.PROVIDER_ID, C.PATIENT_ID FROM (...

Yes, I have. All lookup tables have 1 index (on the ID relational field).

Hi all, I'm having some serious performance issues with my query. All tables are setup with unique indexes. The main table has ~500k rows and most LUTs have <300 rows (except for tblDataConnected, which has ~250k lines). I'm using Access 2010 with an ACCDB database on XP. Not all columns...

OK, so you are using a text box to display the data. We are talking about the same thing here. Hence, my code above still works. Replace 'TextBox' with 'BuyOrSell' and see if you can get it working.

Personally I wouldn't split the table since that is not necessary. You will need a reference in each table to be able to connect the corresponding rows from both tables. The above-proposed setup with the ID references provides excellent ways of managing your data and has little redundancy. Most...

Then the field LoadDate doesn't exist in the table/query ActFuel. You need to check this first. Can you post the field names of ActFuel?

Yes, I understand, but this still doesn't tell me how you display the value, or in what type of control the value is displayed. If you open the properties window of the control it is displayed in, Access will mention the type of control in the first line.

How do you display the value of the data field on the form? Do you use a text box, or something else? Maybe I don't understand instead.

Yes, you are exactly right! I will elaborate a bit, so you can decide for yourself in the future: If specific data in a specific field is very likely to be present in multiple rows, then it is repeatable. Then you can consider to create a look-up table with unique IDs for use as a reference in...

You are getting it now! :) It says 'made non-repeatable', but I guess I should have been more clear. At least the way you say it in your last post you are right, so stick to those ideas! Indeed the referee will be referenced in another table and therefore is repeatable. The date, time and final...

Access 2000 does not properly support conditional formatting unfortunately. You can do this partially by using VBA code: -Open the form properties dialog -Go to event and create a code event for 'On Current' -Insert the following code in your VBA window in the newly created procedure: With...

Check http://en.wikipedia.org/wiki/First_normal_form for a quick example (under 'Examples'). I would do something like this in 1NF setup: SeasonID DivisionID StatusID Date Time StadiumID Attendance HomeTeamID AwayTeamID HomeGoals AwayGoals RefereeID All fields where I added 'ID' to the field...

Are you using Access? Which version?

You are making a few mistakes here: - Comparing a Date field (FuelDate) with a number (Month(LoadDate)) is not possible - You can't compare one field (FuelDate) with two results at the same time (Month([LoadDate]) AND Year([LoadDate])) - You are using a secondary condition which is always true...