Search results

Why not just set the Visible Property of the Controls to True or False. I only use bring to front of send back functions in design mode. And now, with the new stacking and tabular features and anchoring, new since the 2007 version anyway, I never use them. In one of my lastest apps, where it...

Please see my final last comment.

What a morning! Here are my notes from this morning. It was painful, but it is solved. I think the conclusion is that there must have been some corruption associated with the original Screen, and maybe one of the Sub forms in the Navigation Control (NC). I did not work with any of the sub...

I use the same methodology in all of my applications. I have apps connected to Azure SQL DB with various DTU levels, as well as AWS, SQL Server over the Internet running on Dell PowerEdge Servers behind a variety of VPN's and have never run into this issue before. I did not create this...

I altered the Dashboard to have a single tab in the Navigation Control. I removed all combo boxes on the subform (x3) just to render data. I also limited the data to 10 records on the SQL Source Table. The behavior is just the same.

I will add that the Row Source is a Query, not a SELECT Statement. The Recordset Type Property is set to Snapshot. The Combo Box is Limited to List.

There is no code running other than setting the global variables on After Update. As I mentioned, the Combo Box performs perfectly when scrolling down through the list with either the arrow button or mouse and pressing enter. It only occurs when the value is typed into the combo box. There...

I have not done this. I will try it.

I have an NDA on the DB so I cannot show it in any fashion. There is no code other than the After_Update Event that sets the Global Variables for the Filters on the Subform that is in focus on the Navigation Control. The Parent Form is not bound to anything record source. It only acts as a...

Hey Folks, I am a seasoned Access Developer, and I ran into a situation that I have never encountered before. I have an Access App that is connected to a relatively small SQL Server Database hosted by [blank] in the cloud. I have a View that is linked to the DB with the respective Columns for...

No. the "...less" part of the "DSN-less" implies that it does not require a DSN File.

This is just my 1 1/2 cents… I do use TempVars frequently. I have created shortened functions and they work great. As for the phantom record, I would use the After Insert or After Update as opposed to the the Before events. The Before Events are cancellable and that is a problem. Glad you...

Or apply the True Filter Criteria in the Query itself.

Do not use a Sub Query in the Where Clause. Add the [CopyTimeEntry] into your query with the proper joins and then you can refer to any Column within that table. Joins work very similar to where clauses for the purpose of limiting recordsets.

Are you setting the "CallingForm" as a Form Variable or as a String Variable (See Line 30). If a String Variable, this should be fine, but if a Form Variable, you will need to express "Select Case CallingForm.Name" It makes good practice to preface your varaibles with their object tyoe. For...

I don't see where you are defining the Data Connection. The SQL Statement does not know where the data lives. Define the DC and I think you will be good,

Ok.

And that is about the only time I will ever use a Tab Control. I will never use it to host a sub form but for maybe a limited number of exceptions. I prefer the Navigation Control for a variety of reasons, but that is just my preference. I know a lot of people stay away from them, that is...

It is not a problem, per se, but by opting for the Navigation Control, which is already a sub form, it also accomplishes the same purpose as a Tab Control. You get the best of both worlds in one control and eliminate one layer of confusion.

That is where I am at now. Just knowing that it can happen and having a solution in place is how I have proceeded with it as well. There are likely many other quirks that we will never know the exact reason for them.