Search results

It is popular for web based project management systems to use a Kanban board to display actions. So a task would have a status field with for example: assigned, WIP, solved, closed etc. The GUI would display four columns and the tasks would be listed according to their status. To change a status...

That's why I got caught out returning to an old unreleased database that used bound forms, over the last few years I have designed all my forms unbound. A lot more work but a lot more interesting to design.

You are absolutely right Access really doesn't like null bit fields, my first attempt top solve it was in the linked table in Access, that too threw a write conflict. So I have to use an SQL update query in SQL Server Management Studio (SSMS) to set all nulls to 0 then I changed the design in...

I have just experienced a write conflict on a database I designed 3 years ago that sat on a shelf unused. I too was experiencing write conflicts due to null "bit" fields in an SQL database. Never come across this before, more recently my forms have been unbound. Thanks for the link which...

OK, got it, I had selected the wrong ActiveX data object (there were quite a lot). This works: Thanks for all the help.

how do I do that? I suspected it may be down to references, so I got one of me previous database that ran, then from menu went tools > references and made sure all the same boxes were ticked. but that made no difference. The ones I have are:

I am returning to creating databases after a long absence. I am trying to re-use code from previous databases I have designed to save a time. Historically I have a function that checks that the access front end is able to connect to the SQL back end. I have copied this function across to the new...

I guess I am still not getting it. Example at week 1 I have 3 risks with the following impact and probability values stored in the database: Risk 1 > I=5 P=5 Risk 2 > I=5 P=5 Risk 3 > I=5 P=5 The user runs the query and it comes back that there are 3 risks with I=5 and 3 risks are at P=5, all...

thanks

Because I need to keep an ongoing record on a week by week basis of how many risks are at level 5 how many at level 4. Each week I am expected to produce charts for management showing whether the trend over time i.e are high level risks increasing or decreasing. A simple query can only show a...

The two smallint fields contain values from 1 to 5 for each R_ID each week I want to record to a seperate table the quantity of risks at 5,4,3,2,1 etc.

I have a database that stores risks, at any one point there can be many risks with each having values from 1 to 5 for current impact (CI) and current probability (CP). Once a week I would like to tally up how many risks have CI of 5, CI of 4 ......... PI of 5, PI of 4 etc. and store them to a...

OK thanks to all, you got me thinking. The outcome was interesting. I changed the line referencing the range to qualify it as recommended by Gasman. Ran the code and sure enough rngSelection was no longer nothing which was great. But It was still falling over on the next line. Then I noticed...

I hadn't, but I have now, it contains nothing!. Which explains the error, but why would it contain nothing? the wsht object appears valid.

I tend to write inefficient code, as an example one of my databases creates an Excel workbook with two sheets one displaying open issues, the other closed. Both sheets are identical in appearance and hence coded identical, the only difference is the query to generate the data. Up until recently...

Yeh I figured that, pretty tedious though in the MS VBA coding environment as there are so many object properties and it can be difficult to see the "wood for the trees".

I confess to being quite inexperienced in Excel VBA, the methods I use have been created by studying what others have done online, so I may have picked up bad habits. Earlier in the code I had qualified the wsht vaiable (or so I think!) using Set wsht = wbk.Sheets(1) However the link provided...

I have an access database which produces monthly management reports by creating an Excel Workbook from Access using VBA. This has been running hunky dory every month for years. Now all of a sudden I am getting the Error: The standard VBA error code: 1004 The standard VBA error description: No...

David, you are a star, thank you very much, I have spent far too much time trying to track down the problem, but one simple change was all that was needed. I will try to remember that one!

Sorry about that function code below, I have made a few changes it now occurs on line 70. Which suggests it doesn't like query, but as I say if i copy the debug.print of the query into a new query in Access it runs fine. Also if I oaste the query into a new SQL query in SSMS it runs fine there...