Search results

No built in feature that would allow that. Moreover this is something rather complicated to control programatically since you would have to foreseen and manage the many methos of updating a memo field (paste, etc). Unless you go for a posteriori checking and warning (like checking for...

Do a search on 'Not in List'. However, you may have to foresee further checking in your NotInList Event in the case of cascading combos since you probably want to avoid situations like the following one: User selects the value: '1' in Combo1 Combo2 is based on the table...

In theory they can be replicated. However, in practice replication applied to DB objects others than TableDefs and the data inside is a far too unreliable and heavy process (especially when involving forms, reports and modules). MS itslef ackowledges that fact in its white paper on replication...

I would perform a search through all modules to see if I wouldn't have left somewhere a DoCmd.SetWarnings disabling warning messages for some specific action, and not immediatly followed by another SetWarnings statement to re-enable messages. (yes, I read about you macro, but who knows?)

See if the following helps: Open parametered query in code

First, let me say that from first hand (and in a certain number of cases painful) experience, I came to limit to very exceptional cases the use of built and/or 'meaningful' primary keys (as serial numbers, etc) in my DBs. Should I have a natural and useful 'meaningful' candidate for the 'primary...

I believe partial replica are what you are looking after. Have a look to the following references: A97 Partial Replica wizard Replication - Consistent datasets

This is a known Access bug. Disable the Autocorrect option (Tools > Options...), then you will have to re-set a last time your printing layout options for each report.

Guess what... This is a acknowledged bug. There are a variety of workarounds from complex (involving APIs) to simple, like setting your form BorderStyle property to none.

This just goes to show you the principle: (in the OnFormat event of your Detail section) Dim i As Integer For i = 1 To 10 Me.MoveLayout = True Me.NextRecord = False Me.YourControlName= Rnd(324) 'Or Whatever Me.PrintSection = True Next i

Beware with the US date format in your formula. You could create a public function to easily get the fiscal year at anytime: Public Function FinancialYear (dDate as Date) as Integer FinancialYear = Year(dDate)-IIf(dDate <DateSerial(Year(dDate),5,1),1,0) End Function Then, if you don't need...

What is the definitiion of the weeks you need to count for your projection: complete calendar weeks starting on Monday (they can be 51 or 52), just periods of 7 days (they are 52 + 1 or 2 days in a year), other?

Welcome back to the world of the living Tal! Exactly how do you manage the two faces of your personality BukTal?... Or are they just out of your control ? :p

Now that you have (hopefully) redesigned your structure, you will find as I told you much easier to conceive your forms and display your info. Generally, where you have a One to Many relationship between your tables, creating a form (underlying table: One side for the relationship) / subform...

Guldo, You are right that the pb comes from the difference between your regional settings and the date format expected by Access when processing SQL (US date format). You should make a function to wrap the dates you intend to pass to queries: Public Function SQLDate (dDate as Date) As String...

I am not sure I understand where your problem lies, Rich. Not in getting the difference in weeks between two days? [datediff("ww",Date1,Date2)]

You need to create a multiple-fields unique index. In table design view, click on the Indexes toolbar button, enter a name for the index in the first column of the first blank line Select the first field to include in the multiple index, in the second column of the same line. In the 2nd line...

To say the truth I had never created TableDef objects that way (I use SQL), but after some experimentation this is what I came up with: Dim db As Database Dim tdf As TableDef Set db = DBEngine(0)(0) 'Create a new TableDef object Set tdf = db.CreateTableDef("Test") With tdf 'Create and...

Autonumbers are NOT intended for anything but automatically provide an unique identifier. The behaviour you noticed is precisely intended to ensure this purpose. Any attempt to rely on an autonumber for other objectives (like expecting them to be sequencial) is trying to give them a meaning...

What you describe would require 6 tables: TblDiseases -DiseaseID (autonumber PK) -DiseaseName ..? TblDiseasesPerRelatives -DiseaseID (long num foreign key from TblDiseases) -RelativeID (long num foreign key from TblRelatives) -HasDisease (boolean two states: Yes/No) TblRelativesAffectedFamily...