Are you using ADO or DAO?
What I have done to see what kind of records I am getting back is put the source of the recordset into a query and open the query.
szQuery = "SELECT * " _
& " FROM sys_tblqueries " _
& " WHERE hasRun = false " _
&...
In that case... Importing the table will take just as long as running a query against the linked table to make a local table. Did that make sense?
DoCmd.RunSql "SELECT * INTO 'the new table' FROM 'the linked table'
beth,
I don't have SQLServer running at my current location so... I'll have to take a look when I get back to my office tonight. Depending on what you need to do with the table, you could use the ADO objects.
Here is a link to MSDN code examples...
You could do it in code where the function creates the user preferences. This code requires ADO and ADOX (Microsoft ActiveX Data Objects (ADO) 2.8) references and works using MDAC 2.8
You could also create and modify parameters for the query.
Dim cnn As New ADODB.Connection
Dim cat As...
I'll have to make a file for you to download. There is just too much code. I'll try to have it ready for you on monday and give you the url so you can download the mdb.
Thanks,
Dalton
The reason these examples will not work is because he has to use lotus notes.
"Lotus Notes Release 5.0.5 September 22, 2000 for sending/receiving emails. "
What type of recordset are you using?
If you open it as 'adOpenStatic' you will get a recordcount but if you use Dynamic, you will not.
This will return a count.
rs.Open "qryTables", _
cnn, _
adOpenStatic, _
adLockBatchOptimistic
iCount =...
I am sorry that I cannot help with your problem.
My only suggetions are to change where the mdb is backed up or use an external program to zip and backup like 'scheduler'.
This is the correct way to use the 'Left' function.
targetfilename = Left(strFileName, lengte) & "txt"
'The last suggestion has an incorrect use of the 'Left' function.
targetfilename = Left(strFileName, CStr(lengte)) & "txt"
Left(string, length)
The Left function syntax...
I recreated your situation as best I could with the information provided. I have had DoCmd.RunSQL barf on me as well. I decided to make a function to create a query and then delete the query after using it. Hope this helps
If you were using (If (IsNull(DLookup("[ID]"...
Once you have set the record source for the form, make sure one of the controls (hopefully a text box) has tblClient.ClientID as it's control source and reference it to retrieve the id. This will be the first record of the record source so... if you want to have a specific ClientID, indicate...
If you use the wizard to create command button (on the tool box, make sure the control wizards toggle is selected and add a command button to the form), chose Miscellaneous as the category and Run Query as the action. It will prompt you to select the query you would like to run and the code...
Here is the reason:
varFile2(lngIdx, 1) = f_buildNewName(strdirpath, varFile1(lngIdx))
change this line to read:
varFile2(lngIdx, 1) = strdirpath & f_buildNewName(strdirpath, varFile1(lngIdx))
I forgot to add the file spec to the begining of the name.
CopyFile didn't know what to do with...
When I want to change the RowSource of a combo box, I use this methode.
Me!CboUPC.RowSource = "SELECT UPC FROM TblItems " _
& "WHERE CS < " & cboCS.Value & "';"
CboUPC.Requery
Me!CboKras.RowSource = "SELECT Kras FROM TblItems " _...
I created a comboBox that has a record source of various URL's. Then I created an event 'AfterUpdate' to open the link. Is that what you wanted to do?
Private Sub Combo4_AfterUpdate()
Application.FollowHyperlink Combo4.Value
End Sub
Try this:
I have added two functions.
f_buildNewName 'This one creates the new name based off of the old name
f_fileBase 'This one creates the base name i.e. 'Shares','Loans','Certs'
Private Sub Command3_Click()
' Loop through the directory specified in strDirPath and save each
' file...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.