ContactReview :: View topic

bsncp · Experienced Miner

I'm trying to import Lookup values for the Email Merge Code field. I'm getting an error, but I can't see the entire error when the job crashes. Import job srashes on first record. This is all I can see in the error pop-up.

"Server Error: [Microsoft][ODBC SQL Server Driver][SQL Server] Cannot insert the value NULL in..."
File: I:\gx7\gxlookup.prg
Routine: gxlookup
Line: 191

That's all I can see of the error. If there is any way to expand the entire error text I don't know how. I don't have any null fields in my dbase source table. Are there any characters that are "off-limits" in the EmailMergeCode field...like hyphens, periods, etc.? I think I do have a few of those...

Life Ring:
WINDOWS System: Windows NT version 5.01
FREE DiskSpace: 39,469.498 Megabytes
B D E Version: 5.1.1.1
Folder: i:\goldmine\setup\bdeshare\idapi32.cfg
GOLDMINE Exe: i:\goldmine
GMbase: GOLDMINE_SSG_GBX
User: JJS
Sync: ON
GX7 Version: 2009-E
Folder: i:\gx7
Serial #: G7701238
Licensee: SPORT SUPPLY GROUP

OPERATION: LOOKUPS / ZIP ATTACH
Category: LKUP-IMPORT
Description: MergeCodesEmail
Launch ID: LKEMRG3

SOURCE TABLE: c:\docume~1\jstolly\desktop\mergex.dbf
FILTER:
ATTACH POST CD: NO
LL: SOURCE FLD: Mergex->Emailmerge
LL: LKUP LABEL: EmailMergeCodes
LL: FIELD CODE: EMAILMRG
PC: CITY:
PC: STATE:
PC: POSTAL CD:

(END OF LISTING) Created 01/12/2010 11:02:48 AM

GoldBoxGodfather · Experienced Miner

Okay, could you update to the latest, 2010-A, and retry? That'll give me a better read on the error, the line number.

bsncp · Experienced Miner

Thanks, Dave. I ran the import job again after the upgrade and it runs fine. I do have another question related to that field...Did I dream the character limit for the Email Merge Code field was 20 characters? It appears to be just 15.