Error Number 3349
Today's Posts Search Community Links Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Thread Tools Rating: Display Modes 03-09-2009, 12:26 PM #1 v3rse Newly Registered User Join Date: Oct 2008 Posts: 9 Thanks: 0 Thanked 0 Times in 0 Posts Runtime Error 3349 Numeric Field overflow on linked table Hi, I want to import a CSV file into an Access 2003 table. The CSV file have around 53 000 different customer entry. When i do it with the table in the same database, no problem, eveything goes as planned. As soon as i split my database (so the table become linked) and i run the same code, i get the error in topic. Is there any way to solve this? Thanks for your help! v3rse View Public Profile Find More Posts by v3rse 03-09-2009, 03:02 PM #2 RuralGuy AWF VIP Join Date: Jul 2005 Location: @ 8300' in the Colorado Rockies Posts: 13,407 Thanks: 2 Thanked 250 Times in 242 Posts Re: Runtime Error 3349 Numeric Field overflow on linked table Do you understand what the Numeric Field Overflow means? It means you are attempting to put a number in a field that is larger than the field can handle. ie: Integer fields and Single Floating Point fields are suspect. I would not be concerned about linked vs internal at this time. Access might have been helping too much with the Internal table. What version of Access are you using? __________________ (RG for short) aka Allan Bunch Previous MS Access MVP acXP, ac07, ac10, ac13 - WinXP Pro, Win7 Pro, Win10 Pro Please post back to this Forum so all may benefit. Teaching is not filling a bucket but lighting a fire. RuralGuy View Public Profile Find More Posts by RuralGuy 03-10-2009, 05:11 AM #3 v3rse Newly Registered User Join Date: Oct 2008 Posts: 9 Thanks: 0 Thanked 0 Times in 0 Posts Re: Runtime Error 3349 Numeric Field overflow on linked table I'm using 2003 version. I think i'm just gonna show users how to use the import wizard since it's also working using that but that make the apps less user friendly than i would. v3rse View Public Profile Find More Posts by v3rse 03-10-2009, 06:13 AM #4 RuralGuy AWF VIP Join Date: Jul 2005 Location: @ 8300' in the Colorado Rockies Posts: 13,407 Thanks: 2 Thanked 250 Times in 242 Posts Re: Runtime Error 3349 Numeric Field overflow on linked table You defined the tab
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Microsoft Access › Error 3349 How To Fix Microsoft Access Error 3349 Error Number: Error 3349 Error Name:Microsoft Access Error 3349 Error Description: You cannot record your changes because a value you entered violates the settings defined for this table or list (for example, a value is less than the minimum or greater http://www.access-programmers.co.uk/forums/showthread.php?t=167473 than the maximum). Correct the error and try again. Developer:Microsoft Corporation Software:Microsoft Access Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms of Error 3349 "Error 3349" appears and crashes http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/microsoft-access/3349-microsoft-access-error-3349/ the active program window. Your PC frequently crashes with Error 3349 when running the same program. “Microsoft Access Error 3349” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 3349 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Microsoft Access) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 3349 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 3349 Corrupt download or incomplete installation of Microsoft Access software. Corruption in Windows registry from a recent Microsoft Access-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Microsoft Access-related program files. Another progra
is Split If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the http://www.dbforums.com/showthread.php?1211186-Error-3349-(Numeric-Field-Overflow)-Only-If-DB-is-Split forum that you want to visit from the selection below. Results 1 to 6 of 6 Thread: Error 3349 (Numeric Field Overflow) Only If DB is Split Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search https://bytes.com/topic/access/answers/752946-run-time-error-3349-access2k-split-db Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 01-25-06,21:23 #1 davidmound View Profile View Forum Posts Registered User Join Date Jul 2004 Posts 67 Unanswered: Error 3349 (Numeric Field Overflow) Only error number If DB is Split I'm getting the 3349 (Numeric Field Overflow) error when trying to insert new records into a linked back-end table programmatically. The source is a select statement from a linked text file (comma sep). The craziness is two-fold: 1- If I import the destination table to make it local instead of linked, the procedure works fine. But this is a split db, so the table really needs to be linked. 2- I only get error number 3349 the error with certain source text files, not all. So, I can successfully link text file A and select records from it to insert into the linked table Z. And I can link text file B, but in order to select records from text file B and insert them into table Z, I have to actually import table Z (in other words, have a local version of it) rather than have it linked. Any clues? Thanks in advance, David Reply With Quote 01-26-06,05:17 #2 pootle flump View Profile View Forum Posts King of Understatement Join Date Feb 2004 Location One Flump in One Place Posts 14,912 Hi Have you tried explicitly converting the csv value to the data type of the destination since I believe Access has to make a "best guess" of the csv data type and tends to err high (as you would probably want...). E.g. if the destination field is a Long then: Code: INSERT INTO MyDestTable (ColLongData) SELECT CLng(MyCSVCol) FROM MyLinkedCSVFile ??? Testimonial: pootle flump ur codings are working excelent. Reply With Quote 01-26-06,11:32 #3 davidmound View Profile View Forum Posts Registered User Join Date Jul 2004 Posts 67 Thanks for your response. Yes, I tried that. I use CStr, CCur, and CDbl as the converters for the 3 data types that are involved. I think the strangest thing is that it works fi
Question Need help? Post your question and get tips & solutions from a community of 418,536 IT Pros & Developers. It's quick & easy. Run-time error 3349 in Access2K to a Split DB P: 2 Melancholy Man I am getting a Run-time error 3349 when importing a .txt file into the front end of a DB (DB is split). If I use the same specs on the back-end I do not get the error. Is there some file limitation to what can be imported into a front end (linked) table? Note: I am ultimately trying to do the import through VBA in a form on the front end. Any explanation or help greatly appreciated. Dec 27 '07 #1 Post Reply Share this Question 4 Replies P: 2 Melancholy Man I am getting a Run-time error 3349 when importing a .txt file into the front end of a DB (DB is split). If I use the same specs on the back-end I do not get the error. Is there some file limitation to what can be imported into a front end (linked) table? Note: I am ultimately trying to do the import through VBA in a form on the front end. Any explanation or help greatly appreciated. I'm adding to my own issue. I have found that there seems to be a problem with the file specifications. If I use the original specs it works. If I 'Save As' the specs again (changing nothing) and only change the name of the specs. The newly saved specs do not work!! Dec 27 '07 #2 reply Expert Mod 10K+ P: 14,534 MMcCarthy We would actually need to see the code you are using for the import. There is no reason why there should be any difference in importing into the front-end or back-end. Why are you changing the import spec. The point of having one is that it is saved and used thereafter. You may not realise there is a change happening but it sounds like there is. Jan 8 '08 #3 reply P: 1 Reidar I got the same error (3349) when I try to import from Excel into a linked Access table. ----- DoCmd.TransferSpreadsheet acImport, , _ "tblCurrentPrices", rstBatch!DirPath + rstBatch!Filename, True, rstBatch!Range ------ where tblCurrentPrices are linked to the front end app. Any fix to this? Reidar Feb 12 '08 #4 reply Expert Mod 10K+ P: 14,534 MMcCarthy I got the same error (3349) when I try to import from Excel into a linked Access table. ----- DoCmd.TransferSpreadsheet acImport, , _ "tblCurrentPrices", rstBatch!DirPath + rstBatch!Filename, True, rstBatch!Range ------ where tblCurrentPrices are linked to the front end app. Any fix to this? Reidar Link to the spreadsheet and append to the