the following code keeps generating duplicate row as:
POHD_CODE FY ACTIVITY_DATE USER_ID SPRIDEN_ID LAST_NAME ITEM COMM_DESC AMT COAS_CODE
P0469513 10 16-Nov-09 OBLISKD H00446436 Integra Radionics 1 n/a-Extended Warranty on RT Workstation 36285 1
P0469513 10 16-Nov-09 OBLISKD H00446436 Integra Radionics 1 n/a-Extended Warranty on RT Workstation...
User Profile
Collapse
-
Oracle Select Destinct Dups?
-
@hvsummer, thanks for explaining. Mary -
Thank you, however, the vba is still flagging an syntax error on the code.
Code:If IsDate(DateValue(rst_AllText_PRData_Editable_Dates![Contract Effective Date])) = False _ and year(rst_AllText_PRData_Editable_Dates![Contract Effective Date]) NOT Between 2009 And 2025 Then End IfLeave a comment:
-
There is an issue with the syntax for year. Can you pls guide? The pound sign is flagged.
When theCode:If IsDate(DateValue(rst_AllText_PRData_Editable_Dates![Contract Effective Date])) = False _ and year(rst_AllText_PRData_Editable_Dates![Contract Effective Date]) Between #2009# and #2025# Thensyntax is used, it flags it as well.Code:#" &2009& "#
Leave a comment:
-
Detecting an Invalid Date
When a date field contains an invalid date, it needs to be flagged. However, my code is not acknowledging it. For instance, it doesn't recognize 8/15/0007 as a bad date. Any assistance would be appreciated.
...Code:If IsDate(rst_AllText_PRData_Editable_Dates![Contract Effective Date]) = False Then rst_tbl_PRData_Error_Dates.Add rst_tbl_PRData_Error_Dates.[Contract Effective -
Error 3622 Open SQL Server Table with Identity Column
I'm having issues attempting to open a Microsoft SQL table, where the same code has been used in the past without any issues. The error is "Error 3622 Open SQL Server Table with Identity Column." Any assistance would be greatly appreciated.
...Code:Dim dbs As DAO.Database Dim rst_AllText_Credits As DAO.Recordset Dim rst_AllText_SQL_Format_Compare_SQL_Table_Credit_Memo As DAO.Recordset -
dowlingm815 replied to Importing a CSV file that contains trailing spaces - converts it to “á” special charin AccessThe data is exported from a web-base app. the web users appear to be place a space at the end of the field at times. therefore, when it is exported the value is in the CSV file. honestly, i believe the web developers need to look at their data to populate the export field correctly. would you agree?Leave a comment:
-
dowlingm815 replied to Importing a CSV file that contains trailing spaces - converts it to “á” special charin AccessAttached is the file, that doesn't contain many records, it has 4470. The Product Description is the field that contains four records for today's run with the last character equal to "á". The fields will be equal to when imported into access:
SCRUBBRUSH SURG W/ CHLORHEX GLUá
SCRUBBRUSH SURG W/ CHLORHEX GLUá
SCRUBBRUSH SURG W/ CHLORHEX GLUá
CABLE PATIENT MONITOR LNCS - LNC-10á
I am...Leave a comment:
-
dowlingm815 replied to Importing a CSV file that contains trailing spaces - converts it to “á” special charin AccessThe data needs to be imported as its original CSV value. For example, in the CSV file, the product description field contains the following value:
When it is imported into Access, the field is converted into:Code:"SCRUBBRUSH SURG W/ CHLORHEX GLU "
Code:"SCRUBBRUSH SURG W/ CHLORHEX GLUá"
Last edited by NeoPa; Jan 9 '13, 12:36 AM. Reason: [CODE] tags work better. Re-added quotes as delimiters (Duh).Leave a comment:
-
dowlingm815 started a topic Importing a CSV file that contains trailing spaces - converts it to “á” special charin AccessImporting a CSV file that contains trailing spaces - converts it to “á” special char
I need to prevent access from importing a CSV file that contains a field with trailing spaces that gets converted into a special character, such as “á.” The import specification file requires all fields to be imported as text. The import statement is straight forward and doesn’t cause any issues, which is listed below.
...Code:DoCmd.TransferText acImportDelim, "SO_Data Import Specification", "SO_Data", "\\nbpcafile01.core.umdnj.edu\CA\Purchasing\Shared\SCM
-
dowlingm815 replied to Passing a field to be deleted - contains Special Chars - function doesn't acknowledgein AccessWhen altering, the parameter without the brackets, the function acknowledges the field.
The tables in the db, get uploaded to a SQL db. Applications reference the SQL table that use the same field names from the imported file.Leave a comment:
-
dowlingm815 replied to Passing a field to be deleted - contains Special Chars - function doesn't acknowledgein AccessI totally agree; however, this is data that is extracted from an external system. I have no control over the import field.Leave a comment:
-
dowlingm815 started a topic Passing a field to be deleted - contains Special Chars - function doesn't acknowledgein AccessPassing a field to be deleted - contains Special Chars - function doesn't acknowledge
There is a field that contains special character when it is passed to a function, it doesn't acknowledge that the field exist in the table. When I remove the special chars, it passes the field and performs a delete on the field.
The field name is [Sales Order Date/Time Created] from table SO_Data.
Thank you in advance for your assistance.
The sub that calls the functions:
...Code:If ifFieldExists("[Sales -
i modified the code using the IsNull in the following matter.
...Code:If IsNull(strTEMP_CORD_No) Then If IsNull(rstTemp!CORD_No) Then strTEMP_BANNERPOAmt = strTEMP_BANNERPOAmt + rstTemp!BANNERPOAmt End If Else If strTEMP_CORD_No = rstTemp!CORD_No Then strTEMP_BANNERPOAmt = strTEMP_BANNERPOAmt + rstTemp!BANNERPOAmtLeave a comment:
-
When Null field = Null field, the results are FALSE?
When testing the following code, the results should be true, however, a false results is generated. I don't understand why and i need to maintain the data values.
Code:If strTEMP_CORD_No = rstTemp!CORD_No Then strTEMP_BANNERPOAmt = strTEMP_BANNERPOAmt + rstTemp!BANNERPOAmt Else MsgBox "cord no not equal" End If -
NeoPa, the value is 12.
Rabbit, the quotes have been removed.Leave a comment:
-
i'm not sure i follow your direction. the issue is on line 36 at the "where" clause when the form parameters are reference.Leave a comment:
-
Too few parameters. Expected 1
I have a SQL statement to call data using a form. however, it keeps generating a "[3061]: Too few parameters. Expected 1" error.
I've attempted to convert it to queryDef, however, no progress has been made.
Any guidance, would be appreciated.
the original code is as such:
...Code:Dim dbs As DAO.Database Dim rstTemp As DAO.Recordset Dim strSQL As String Set dbs = CurrentDb()
Last edited by NeoPa; Oct 17 '11, 04:40 PM. Reason: Merged both parts of the single question into a single request post. -
Thank you, totally ignored that situation, which in past, I was well aware of that error.Leave a comment:
-
VBA Create Table Statement - Syntax Error - Need Fresh Eyes
Hi,
I need fresh eyes to see where my syntax error is occurring.
Any assistance would be appreciate.
Mary
...Code:CurrentDb.Execute ("CREATE TABLE tbl_FYData(PIDM Integer, " & _ "FY Varchar(2), " & _ "[PO Trans Date] DATETIME, " & _
No activity results to display
Show More
Leave a comment: