I mentioned in post 27 or 28 that Memo would result in an error.
If you look at the intro in the latest version:
Code:
----------------------------------------------------------------
' Procedure Name: CreateLKTables
' Purpose: Create the LK_ tables and populate with data from the Org tables.
'
' Will create and populate datatypes text, number, long, double, currency
' Memo and others are not supported and will result in a Custom Error if found
' Procedure Kind: Sub
' Procedure Access: Public
' Author: Jack
' Date: 17-Mar-21
I do not handle Memo, attachment datatypes with this set up.
I was suggesting that some datatypes don't work with various constructs.
For example, table data macros don't work with memo, attachment, multivalue...
You'll see I have coded to display Custom Errors for Memo and other data types
Code:
....
190 Case "Memo" 'unlikely in the application
'Raise custom error --unsupported can't have memo as pk
200 Err.Raise 5095, , "LK_" & rsFields!Field_Name & " LKRelated: Memo datatype not supported"
210 GoTo GetNext
220 Case Else 'other non supported type -allow for anything else
'Raise custom error unsupported datatype
230 Err.Raise 5096, , " LKRelated: Some unsupported datatype " & rsFields!Data_Type
240 GoTo GetNext
I was testing with a few datatypes and the code supports text, number, double and currency.
A Memo/Longtext field can not be a primary key. And long text without some qualifying info makes little sense.
A single field, memo datatype file would be like a series of unrelated paragraphs or descriptions.
If you need Memo support, then I suggest you give me some representative test data and we can design a solution.
I have used memo fields for Company Descriptions, Product/Service descriptions, NAICS descriptions, Marketing description- in English, French and in some case Spanish. But they were always identified with a Type, Language and related Company/Product etc.