Search results for query: *

A long shot this one, but does the database compact and repair OK? I ask because I read about a 'DECOMPILE' option that I've used a few times that suggests that not all compiled code is removed in certain circumstances and using it did solve a couple of odd problems for me. I'm certain I read...

If all fields flickering then I would guess that somewhere you have refresh/requeries cascading - I used to get this on a complex subform I inherited. The bad news is that you may have to put in break points and step through code, I did and even then I also found refreshes in the event...

If I understand you correctly, Yes, there are a few ways but being a programmer they are all in Code depending upon how I open the form. *********** If you use doCmd a) In your button to pop up the frmTestScenarios add an OpenArgs (I think that is the name - I'm not at my Access PC so can't...

I think you have made an error in keying, Note the Sum is MyValues_1 not MyValues in the original SELECT MyValues.Name, MyValues.Value, Sum(MyValues_1.Value) AS Total FROM MyValues INNER JOIN MyValues AS MyValues_1 ON MyValues.Name = MyValues_1.Name GROUP BY MyValues.Name, MyValues.Value; I...

Not sure if this maybe a registry issue, my DB only exports 32K records before complaining and aborting the export - try Microsoft sites.

...checking. BUT a) the design should be fine, and b) debugging can be hours of fun ;-) dim rs as DAO.Recordset dim strSQL as string dim varMyField '** not sure about adOpenTable argument below, '** you need to check spelling etc set rs=CurrendDb.openrecordset(tblEmplInfo, adOpenTable)...

I am assuming that 'BrowseForFile' is a function of yours, and it is there that the 'browse window' should appear? If so the code for BrowseForFile would seem to be the problem, not this code.

I had so much help from people in here when I first started Access that it's good to feel I contributed for a change! Good luck with the export.

One way is,I think, a matter of knowing the hierarchy of the sub form fields then setting the 'total field' to the sum of them, eg =[forms]![myParentForm]![subForm1]!subTotalField + [forms]![myParentForm]![subForm2]!subTotalField (my syntax above is probably not accurate, as Access isn't my...

If you have imported the CSV file, then you have it in a table, however I would then be looking at a Query to create a new table from your imported table, manipulating the data in the process. If you read up on queries and play around in the 'Query by Example' grids that appear if you select...

I think you need to return a variant from your function, as otherwise it is expecting a date variable.

Simple export into Excel wouldn't be a problem, where a new excel file is created and the data 'streamed in by Access', but exporting to a specified region, would, I think,need VBA , as I think you would need to point to each cell in the region into which you want to add the information.

I'm not at my Access PC so cannot look up the syntax of DateAdd, and not knowing how you intend to record the booking period (eg fromDate to toDate or fromDate for x days) I would look at a loop using the dateAdd function to generate the booking date, and add a new records on each iteration of...

No, but if this is claimed to do it, I would experiment with values other than 0 in the TwainSelect brackets.

Assuming that you are not setting the 'has module' properties of the forms to 'No', then suspect corruption of the database. Take a copy then look at the following site for help - maybe use 'decompile'and see if that helps. The link below is useful...

You need to enclose text within single quotes as "Company=' " & Me.Company & "'"

I found comments on the site below, http://www.adopenstatic.com/faq/80040e21.asp and also found the one below, although this is for an ASP front end, where the data input is less restricted. "Right, I just solved the problem. The length of the field in the database was too short.&quot...

I'm still checking, but one possibility is that you need to upgrade you MDAC, as this is one of the MS explanations of this message. Microsoft OLE DB Provider for ODBC Drivers error '80040e21' The request properties can not be supported by this ODBC Driver. If I find anything more relevant...

I'm not in front of my Access PC so some of my terminology may be a bit out, but if you look at the ALL tab of your properties, for any Text box you will have it's name property and below it should be the name of any bound field. IF you have a record source set for the form, you shouldn't need...

You need to open the sub form using acNewRecord as a parameter, using DoCmd if I recall correctly. (I'm not on my Access development PC so I can't lookup the correct syntax)