I'd say that you can't really view XML in that way.
It's essentially only a standard. Fairly revolutionary in data terms - but just as html was in internet formats.
Using it as an underlying file format (still somewhat obfuscated by binary data) doesn't ultimately mean that much in the grand...
Can I just confirm - when you say "changing everything from accdb to mdb" did you also then either switch to a PC running Access 2003 or earlier (or install 2003 on that previously slow PC)?
If not - then you're still using ACE. The format of the application won't change the engine that's...
Chris is right about the cause of this error.
The table in question is, presumably local, where others haven't been in the past?
This would cause the default recordset type to be TableType and hence the FindFirst method not supported.
Simply specifying a Dynaset circumvents that.
The...
No worries and no worries. ;-)
There's every chance that you will need a TimeStamp column (if you've unassigned Bits or Floating Point precision column types).
And a TimeStamp can give certain performance advantages.
It can have side effects though with two subforms pointing to the same...
Do you have a Timestamp column in the SQL tables involved in both form's sources?
If so, do you need it?
Failing that, you can always grab the read only form's source by an alternative method than the editable form's. For example it's read only nature would make it a good option for a...
I'm assuming that even the number of parameters can't be prediucted either - hence reason why Run wasn't considered?
Included for such dynamic execution as part of the Application OM for each Office app (shock horror - consistency! ;-p).
i.e. more targeted than Eval. Less specific than...
Very quick bit of background...
By opening the recordset using the Execute method of a command or connection object (cmd.Execute) you are acquiring a ForwardOnly recordset cursor type.
It doesn't support the RecordCount property.
Even though you were attempting to request other types, such as...
Hi
Yeah 25 minutes does sound pretty lame - but then that's over 5 rows a second. Bearing in mind that each one is performed as an individual insert - it becomes less shocking. It's exactly that kind of latency that means you want to avoid the local join and the 8K records means you don't want...
I agree that you ideally want to avoid the heterogeneous join. (Such an inefficient query request.)
Building an In clause by which to filter will be a reasonable solution if
a) you don't have all that many local records and
b) you don't need to inlude fields from the local table (I kinda get the...
fOSUsername as in: http://www.mvps.org/access/api/api0008.htm
??
Expressions used in Table Definitions are confined by the limitations of the native Jet expression service - not that enhanced by Access. (It's a necessary safeguard - build a Jet DB and access it externally without Access to...
A recordset would have to be opened directly against the server of course - otherwise you'll again fall foul of Jet's 255 column limit. (It's not an Access limitation per se.)
Since you mention updatability then a passthrough isn't much help to you.
Your mention of creating a View on the...
The formatting you require will need HTML content in the email (you could perhaps hack it into submission with a fixed width font - but it would't be my preference personally.
Have a look at this thread for some suggestions and a link perhaps...
You have two issues.
Firstly TSQL doesn't allow you to refer to aliased columns within the same query.
If that's a shocking inconvenience (which it could be) you can perform your aggregation and aliasing first in a subequery, and then refer to the aliases just fine from the parent query.
e.g...
If you wanted to do this as a query, something like:
UPDATE tblrec
SET
[list] = Replace(Replace(
[list], Chr(13) & Chr(10), Chr(10)), Chr(10), Chr(13) & Chr(10))
WHERE
[list] Like "*" & Chr(10) & "*"
Cheers.
Your suspicion is correct.
It's not that there's a problem with the Memo field though.
It's simply the Access UI itself, whose controls don't recognise the single LineFeed as such. They do indeed demand a Carriage Return and Line feed... vbCrLf or Chr(13) & Chr(10).
Depending upon the process...
Just to be clear, I'll re-iterate from the threads I pointed to and expand based on memory.
The First and Last functions are descriptive of what they do. But it is not what is commonly perceived or expected.
They return the value from the first or last selected row.
This is the row as it is read...