Search results for query: *

From an Access performance FAQ: __________________________________________________________________________________________________________________________ (LDB locking which a persistent recordset connection fixes) When the symptoms encountered indicate that performance is acceptable with a...

In my database, I'm trying to make it so that a user may only edit the records of a table through a data access page (DAP), and not through the table itself. I know that this is already covered in the Access Security FAQ (Item 25), but I'm having a hard time understanding what it wants me to do...

Is there any way to make it so that certain objects, such as text boxes, load before everything else in a report? In my case, I have a text box that prompts an input box and returns a set of values, which the rest of the data in the report depends on. The problem is, sometimes this text box...

Ehh, there's a small problem. If there are values defined for each of the text boxes, then the report returns the relevant values perfectly. If they're blank, though, it doesen't prompt me for values and the report just kind of sits there. Any ideas?

Thanks you two. Subform/subreport creation can be found in the toolbox (the button is in the rightmost column, second to last row for the default setup). Make sure you have the wizard turned on.

I have two queries, SQL is as follows: SELECT DISTINCT GAPS.GAPID FROM GAPS WHERE (((Month([Recieved]))=[Enter month (1-12):]) And ((Year([Recieved]))=[Enter year (yyyy):]) And (([GAPS].[Track])="EDI") And (([GAPS].[Status])="Completed")); SELECT DISTINCT GAPS.GAPID FROM...

Here is the way that my database is set up right now: 1 head guy < admin, access to everything 4 developers < users, access only to their specific reports, + the access page (which requires the edit permission for the table) Right now, the access page prompts the user on opening with a...

That did it. The main report takes a bit longer to load now, but at least it works. Thanks.

The thing is, I was planning to insert this into a main report as a subreport (one of many fields in a table). Is there at least some way to prevent it from displaying &quot;#Error&quot;? Blank is good too.

I have a report based on a query (from another question I had asked here) - here's the SQL example: SELECT Count(*) AS Cnt, GAPS.GAPID FROM GAPS WHERE *** (whatever criteria) GROUP BY GAPS.GAPID; Because of the &quot;GROUP BY&quot; statement, if no records match this criteria, then opening the...

Never mind. Thanks for your help.

&quot;Data type mismatch in criteria expression&quot; SELECT Count(*) AS Cnt, GAPS.IDGAPID, GAPS.BSR FROM GAPS GROUP BY GAPS.IDGAPID, GAPS.BSR having (((GAPS.BSR)=2))

I think that the SQL GROUP BY statment would work, but I'm having a little problems. When I add the GROUP BY statement I get an error. Here's the original: SELECT GAPS.SeqNumber, ... ,GAPS.DaysRemaining FROM GAPS WHERE ((GAPS.Status)=&quot;Completed&quot;); Here's the modified ( /w syntax...

...where does that go exactly?

OK - What I have now is a bunch of queries, a bunch of subreports to count the records returned by those queries, and finally, a few main reports to enter those subreports into. Here's the problem: A given query has a [GAP ID] field and a [BSR] field. Records can have the same &quot;GAP...

That was actually quite helpful. Thanks.

...is there a way? Thanks.

&quot;The database has been placed in a state by an unknown user that prevents it from being opened or locked.&quot; The above is the error that I frequently get when some script of mine runs that creates ADO connections. Apparently, the reason is that I'm creating the connection implicitly...

Thanks very much.

I've ended up having to rename one of the fields in my table. Ideally I'd just work around it, but it ends up creating some big problems down the line. Is there any way to update all of my queries/reports for this field without having to manually edit all 900+ of them? It'll only take me a day...